Methods and systems for dynamic spectrum arbitrage user profile management

ABSTRACT

A dynamic spectrum arbitrage (DSA) system includes a home subscriber server (HSS), a mobility management entity (MME), an eNodeB, a dynamic spectrum controller (DSC), and a dynamic spectrum policy controller (DPC). The DSC may receive resource allocation information from the DPC, and send updated information and instructions to the HSS. The HSS may be configured to receive information from the DSC, detect changes to HSS subscription information (e.g., user profile information), determine whether the changes affect the information managed/stored by an MME component, and send the detected changes to the MME component when the HSS determines that the changes affect the information managed/stored by the MME. The MME component may use the information included in the received messages to add, remove, or modify the MME&#39;s stored subscription information or user profile information. The MME component may then communicate these updates, additions, or changes to the HSS component.

RELATED APPLICATIONS

This application claims the benefit of priority to U.S. ProvisionalApplication No. 61/828,335, entitled “Methods and Systems for DynamicSpectrum Arbitrage User Profile Management” filed May 29, 2013, theentire contents of which are hereby incorporated by reference.

BACKGROUND

With the ever increasing use of wireless communication devices foraccessing networks and downloading large files (e.g., video files),there is an increasing demand for radio frequency spectrum. Smart phoneusers complain about dropped calls, slow access to the Internet andsimilar problems which are due largely to too many devices trying toaccess finite RF bandwidth allocated to such services. Yet parts of theRF spectrum, such as the RF bands dedicated to emergency services (e.g.,police, fire and rescue, etc.), go largely unused due to thenon-continuous and episodic employment of such voice-radio communicationbands. Therefore, improved methods and solutions for dynamicallyallocating underutilized telecommunication resources (e.g., RF spectrum,etc.) of a first telecommunication network for access and use bywireless devices that subscribe to other networks will be beneficial tothe telecommunication networks, service providers, and to the consumersof telecommunication services.

SUMMARY

The various embodiments include a dynamic spectrum arbitrage (DSA)system that includes a home subscriber server (HSS) having a HSSprocessor, a mobility management entity (MME) having a MME processorthat is coupled to the HSS via a first communication link, an eNodeBhaving an eNodeB processor that is coupled to the MME via a secondcommunication link, a dynamic spectrum controller (DSC) having a DSCprocessor that is coupled to the eNodeB via a third communication link,and a dynamic spectrum policy controller (DPC) having a DPC processorthat is coupled to the DSC via a fourth communication link.

In an embodiment, the HSS processor may be configured with processorexecutable instruction to perform operations that include determiningwhether a HSS information (e.g., HSS user profile information) stored ina memory of the HSS has changed for a wireless device, determiningwhether the changes affect user profile information stored in a userprofile repository of the MME in response to determining that the HSSinformation has changed, generating an changed data communicationmessage that includes information identifying the changes, and sendingthe generated changed data communication message to the MME via thefirst communication link.

In a further embodiment, the MME processor may be configured withprocessor executable instruction to perform operations that includereceiving the changed data communication message via the firstcommunication link, and adding user profile information included in thereceived changed data communication message to the user profilerepository. In a further embodiment, the MME processor may be configuredwith processor executable instruction to perform operations that includereceiving the changed data communication message via the firstcommunication link, and using information included in the receivedchanged data communication message to modify user profile informationstored in the user profile repository.

In a further embodiment, the MME processor may be configured withprocessor executable instruction to perform operations that includereceiving the changed data communication message via the firstcommunication link, using information included in the received changeddata communication message to determine whether a public data network(PDN) subscription context has a related active PDN connection in theMME, determining whether a subscribed quality of service (QoS) profilehas been modified, and performing an subscribed QoS modificationoperation in response to determining the QoS profile has been modified.

In a further embodiment, the MME processor may be configured withprocessor executable instruction to perform operations that includedetermining whether subscription data and a mobile management context ofa detached wireless have been deleted, and sending a purge communicationmessage to the HSS via the first communication link in response todetermining that the subscription data and a mobile management contextof a detached wireless have been deleted.

In a further embodiment, the HSS processor may be configured withprocessor executable instruction to perform operations that includereceiving the purge communication message via the first communicationlink, and setting a purge flag in response to receiving the purgecommunication message.

In a further embodiment, the DPC processor may be configured withprocessor executable instruction to perform operations that includereceiving a resources withdrawn communication message from a second DSCindicating that resource submitted for auction should be withdrawn fromthe auction, and sending the received resources withdrawn communicationmessage to the DSC via the fourth communication link.

In a further embodiment, the DSC processor may be configured withprocessor executable instruction to perform operations that includereceiving the resources withdrawn communication message from the DPC viathe fourth communication link, and sending a request to delete a closedsubscriber group identifier associated with the withdrawn resource tothe eNodeB via the third communication link.

In a further embodiment, the eNodeB processor may be configured withprocessor executable instruction to perform operations that includereceiving the request to delete the closed subscriber group identifierfrom the DSC via the third communication link, updating a list of activeresources by removing the closed subscriber group identifier from thelist of active resources, generating a configuration update commutationmessage that includes the updated list of active resources, and sendingthe configuration update commutation message to the MME via the secondcommunication link.

In a further embodiment, the DSC processor may be coupled to the HSS viaa fifth communication link, and the DSC processor may be coupled to theMME via a sixth communication link. In a further embodiment, the HSSprocessor may be configured with processor executable instruction toperform operations that include receiving updated HSS information fromthe DSC via the fifth communication link, determining whether theupdated HSS information affects the user profile information that isstored in a user profile repository of the MME, generating an changeddata communication message that includes information identifying thechanges, and sending the generated changed data communication message tothe MME via the first communication link.

Further embodiments include a dynamic spectrum arbitrage (DSA) methodsfor synchronizing information, which may include determining in aprocessor of a home subscriber server (HSS) whether HSS information thatis stored in a memory of the HSS has changed for a wireless device,determining whether the changes affect user profile information that isstored in a user profile repository of a mobility management entity(MME) in response to determining that the HSS information has changed,generating an changed data communication message that includesinformation identifying the changes, and sending the generated changeddata communication message to the MME.

In an embodiment, the method may include receiving the changed datacommunication message in a MME processor of the MME, and adding userprofile information included in the received changed data communicationmessage to the user profile repository of the MME. In a furtherembodiment, the method may include receiving the changed datacommunication message in a MME processor of the MME, and usinginformation included in the received changed data communication messageto modify user profile information stored in the user profile repositoryof the MME. In a further embodiment, the method may include receivingthe changed data communication message in a MME processor of the MME,using information included in the received changed data communicationmessage to determine whether a public data network (PDN) subscriptioncontext has a related active PDN connection in the MME, determining bythe MME processor whether a subscribed quality of service (QoS) profilehas been modified, and performing by the MME processor an subscribed QoSmodification operation in response to determining the QoS profile hasbeen modified.

Further embodiment include a home subscriber server (HSS) that includesa memory and a processor coupled to the memory and configured withprocessor executable instruction to perform operations that includeestablishing a first communication link to a mobility management entity(MME) server; determining whether HSS information stored in the memoryhas changed for a wireless device, determining whether the changesaffect user profile information stored in a user profile repository of amobility management entity (MME) in response to determining that the HSSinformation has changed, generating an changed data communicationmessage that includes information identifying the changes, and sendingthe generated changed data communication message to the MME via thefirst communication link. In a further embodiment, the HSS processor maybe configured with processor executable instruction to performoperations further including establishing a second communication link toa dynamic spectrum controller (DSC) server, receiving a request forsubscriber information from the DSC via the second communication link,and sending the HSS information to the DSC in response to receiving therequest. In a further embodiment, the HSS processor may be configuredwith processor executable instruction to perform operations such thatgenerating the changed data communication message includes generatingthe changed data communication message to include information fordetermining whether a public data network (PDN) subscription context hasa related active PDN connection in the MME. In a further embodiment, theHSS processor may be configured with processor executable instruction toperform operations such that generating the changed data communicationmessage includes generating the changed data communication message toinclude information for determining that a subscribed quality of service(QoS) profile has been modified for the wireless device.

Further embodiments include computing devices having a processor (orprocessing core) configured with processor-executable instructions toperform various operations corresponding to the operations/methodsdiscussed above.

Further embodiments include computing devices that include various meansfor performing functions corresponding to the operations/methodsdiscussed above.

Further embodiments include a non-transitory processor-readable storagemedium having stored thereon processor-executable instructionsconfigured to cause a processor/processing core to perform variousoperations corresponding to the operations/methods discussed above.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and constitutepart of this specification, illustrate exemplary embodiments of theinvention, and, together with the general description given above andthe detailed description given below, serve to explain features of theinvention.

FIGS. 1A through 1E are system block diagrams illustrating variouslogical and functions components and communication links incommunication systems that may be used to implement the variousembodiments.

FIG. 2A is a process flow diagram illustrating a dynamic spectrumarbitrage (DSA) method of allocating resources from the perspective of adynamic spectrum policy controller (DPC) in accordance with anembodiment.

FIG. 2B is a message flow diagram illustrating message communicationsbetween components of a DSA communication system when allocatingresources in accordance with an embodiment.

FIGS. 3 through 7 are process flow diagrams illustrating an embodimentDSA method of allocating and accessing resources in a communicationsystem that includes a DPC, two dynamic spectrum controllers (DSCs), anda wireless device.

FIGS. 8A through 8C are message flow diagrams illustrating an embodimentdynamic spectrum arbitrage application part (DSAAP) registration method.

FIGS. 9A and 9B are message flow diagrams illustrating an embodimentDSAAP advertising method.

FIGS. 10A and 10B are message flow diagrams illustrating an embodimentDSAAP method for communicating a list of available resources.

FIGS. 11A and 11B are message flow diagrams illustrating an embodimentDSAAP bidding method.

FIGS. 12A through 12D are message flow diagrams illustrating anembodiment DSAAP notification method for informing participatingnetworks of the results of the bidding operations.

FIGS. 13A and 13B are message flow diagrams illustrating an embodimentDSAAP purchase method for immediately (or near immediately) purchasing aresource.

FIGS. 14A and 14B are message flow diagrams illustrating an embodimentDSAAP allocation method for allocating resources in a lessor network foraccess and use by components in a lessee network.

FIGS. 15A and 15B are message flow diagrams illustrating an embodimentDSAAP backoff method of selectively handing over a wireless device froma lessor network back to the lessee's network (i.e. its home PLMN).

FIG. 16A is a message flow diagram illustrating an embodiment DSCinitiated DSAAP de-registration method for terminating DSA operations.

FIG. 16B is a message flow diagram illustrating an embodiment DPCinitiated DSAAP de-registration method for terminating DSA operations.

FIG. 17A is a message flow diagram illustrating a DSC initiated DSAAPerror indication method for reporting errors.

FIG. 17B is a message flow diagram illustrating a DPC initiated DSAAPerror indication method for reporting errors.

FIGS. 18A and 18B are message flow diagrams illustrating embodiment userprofile management methods.

FIG. 18C is a message flow diagram illustrating an embodiment DSC methodof requesting subscriber data from a home subscriber server (HSS).

FIG. 19 is a process flow diagram illustrating an embodiment HSS methodof updating user profile information in a mobility management entity(MME).

FIG. 20 is a process flow diagram illustrating an embodiment MME methodof updating user profile information and modifying the quality ofservice (QoS) level for a wireless device based on the updated userprofile information.

FIG. 21 is a component block diagram of an example wireless devicesuitable for use with the various embodiments.

FIG. 22 is a component block diagram of a server suitable for use withan embodiment.

DETAILED DESCRIPTION

The various embodiments will be described in detail with reference tothe accompanying drawings. Wherever possible, the same reference numberswill be used throughout the drawings to refer to the same or like parts.References made to particular examples and implementations are forillustrative purposes, and are not intended to limit the scope of theinvention or the claims.

As used herein, the terms “mobile device,” “wireless device” and “userequipment (UE)” may be used interchangeably and refer to any one ofvarious cellular telephones, personal data assistants (PDA's), palm-topcomputers, laptop computers with wireless modems, wireless electronicmail receivers (e.g., the Blackberry® and Treo® devices), multimediaInternet enabled cellular telephones (e.g., the iPhone®), and similarpersonal electronic devices. A wireless device may include aprogrammable processor and memory. In a preferred embodiment, thewireless device is a cellular handheld device (e.g., a wireless device),which can communicate via a cellular telephone communications network.

As used in this application, the terms “component,” “module,” “engine,”“manager” are intended to include a computer-related entity, such as,but not limited to, hardware, firmware, a combination of hardware andsoftware, software, or software in execution, which are configured toperform particular operations or functions. For example, a component maybe, but is not limited to, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program, acomputer, a server, network hardware, etc. By way of illustration, bothan application running on a computing device and the computing devicemay be referred to as a component. One or more components may residewithin a process and/or thread of execution and a component may belocalized on one processor or core and/or distributed between two ormore processors or cores. In addition, these components may execute fromvarious non-transitory computer readable media having variousinstructions and/or data structures stored thereon.

A number of different cellular and mobile communication services andstandards are available or contemplated in the future, all of which mayimplement and benefit from the various embodiments. Such services andstandards include, e.g., third generation partnership project (3GPP),long term evolution (LTE) systems, third generation wireless mobilecommunication technology (3G), fourth generation wireless mobilecommunication technology (4G), global system for mobile communications(GSM), universal mobile telecommunications system (UMTS), 3GSM, generalpacket radio service (GPRS), code division multiple access (CDMA)systems (e.g., cdmaOne, CDMA2000™), enhanced data rates for GSMevolution (EDGE), advanced mobile phone system (AMPS), digital AMPS(IS-136/TDMA), evolution-data optimized (EV-DO), digital enhancedcordless telecommunications (DECT), Worldwide Interoperability forMicrowave Access (WiMAX), wireless local area network (WLAN), publicswitched telephone network (PSTN), Wi-Fi Protected Access I & II (WPA,WPA2), Bluetooth®, integrated digital enhanced network (iden), landmobile radio (LMR), and evolved universal terrestrial radio accessnetwork (E-UTRAN). Each of these technologies involves, for example, thetransmission and reception of voice, data, signaling and/or contentmessages. It should be understood that any references to terminologyand/or technical details related to an individual telecommunicationstandard or technology are for illustrative purposes only, and are notintended to limit the scope of the claims to a particular communicationsystem or technology unless specifically recited in the claim language.

A high priority in responding to any emergency or disaster situation isestablishing effective communications. In large scale emergency ordisaster (both manmade and natural) situations, it is paramount tomaintain communications between all first responders and emergencypersonnel in order to respond, manage, and control the emergencysituation effectively. In the absence of effective communication amongfirst responders and other emergency personnel, resources may not beeffectively mobilized to the areas which need the resources most. Evenin minor emergency situations (e.g., traffic accidents and fires), firstresponders must be able to call on support assets and coordinate withother services (e.g., public utilities, hospitals, etc.).

With the ubiquity of wireless device ownership and usage, emergencycommunication via wireless devices using commercial cellularcommunication networks often are the most efficient and effective meansto mobilize emergency response personnel and resources. Enablingwireless devices to provide effective emergency communications obviatesthe technical challenges and expense of coordinating radio frequenciesamong various first responder agencies (e.g., police, fire, ambulance,FEMA, public utilities, etc.). Also, qualified first responders to anaccident who are off duty or not ordinarily equipped with radios (e.g.,doctors, nurses, retired police, or military personnel) will have or canquickly borrow a wireless device.

Emergency communications over cellular communication networks is notwithout problems, however. Cellular and other telecommunication networks(“networks”) are designed to accommodate access requests from only afraction of the total number of wireless devices in a particular cell.At times of emergency or crisis, network resources may become overtaxedwhen predictable human responses to the situation prompt anextraordinary number of wireless device users within a particular cellto access the network at the same time. Wireless device users may beattempting to alert emergency personnel of the emergency situation (suchas a 911 emergency call) or to alert friends or family members that theuser is safe despite being in the area of an emergency situation. Someusers may be transmitting images of the emergency condition (fire,accident, etc.) to news services or friends. In a wide scale situation,emergency responders using wireless devices for emergency communicationswill add to the call volume. Regardless, the predictable increase incall volume during an emergency situation can overwhelm a commercialcellular communications network, particularly in the cell zoneencompassing the emergency, thus rendering the network unreliable foremergency response personnel communication usage.

To overcome these and other limitations of existing solutions, thevarious embodiments include components configured to provide tieredpriority access (TPA) capabilities to deliver quality of service (QoS)and grade of service (GoS) based wireless device communications forfirst responders. Detailed descriptions of example TPA systems areprovided in U.S. Pat. No. 8,275,349 dated Sep. 25, 2102, the entirecontents of which are hereby incorporated by reference in their entiretyand for all purposes.

In overview, a TPA system or solution may include various componentsconfigured to perform various TPA operations to coordinate, makeavailable and/or provide wireless communication resources to highpriority users (e.g., emergency personnel) during times of highcongestion or in emergency situations. For example, TPA components maybe configured to monitor a wireless network's call volume, determinewhether the wireless network call volume exceeds a first pre-determinedthreshold, partition the wireless network resources based on prioritieswhen the wireless network call volume exceeds the first pre-determinedthreshold, and reserve a portion of the partitioned resources for highpriority usage (i.e., use by wireless devices of authorized emergencypersonnel). The TPA components may be further configured to monitorincoming and outgoing calls to determine whether a call is made from orto an high priority device (e.g., to or from a pre-registered wirelessdevice or wireless devices of authorized emergency personnel), allowgeneral access to the wireless network resources so long as no call ismade from or to high priority device, and restrict general access to thewireless network resources in response to determining that a call ismade to or from a high priority device. As such, TPA solutions allowtelecommunication systems use more the available resources, and ensurethat high priority users can access and use the system when needed.

In the various embodiments, these and other TPA operations may beperformed in (or in conjunction with) a dynamic spectrum arbitrage (DSA)system configured to dynamically manage the availability, allocation,access, and use of telecommunication resources (e.g., RF spectrum, etc.)between two or more networks (e.g., between a lessor network and alessee network). A detailed description of an example DSA system isprovided in U.S. Pat. No. 8,711,721 dated Apr. 29, 2014, the entirecontents of which are hereby incorporated by reference in their entiretyand for all purposes.

Briefly, a DSA system may include a dynamic spectrum policy controller(DPC) configured to manage the DSA operations and interactions betweentwo or more networks (e.g., between a lessor network and a lesseenetwork). The DPC may communicate with various network components in anetwork provider network either directly or through one or more dynamicspectrum controller (DSC) components. For example, the DPC maycommunicate with a Home Subscriber Server (HSS), either directly or viaa DSC. The HSS may be a master user database that stores/includes thesubscription-related information (i.e., subscription-profile, userprofile, etc.) and information about subscriber's location and IPinformation. That is, the HSS may store subscription information foreach wireless device, such as a subscribed QoS profile, accessrestrictions for roaming, etc. In addition, the HSS may storeinformation about the packet data networks (PDNs) to which the wirelessdevices are allowed to connect. For example, the HSS may store an accesspoint name (APN) or a PDN address that indicates one or more subscribedIP addresses. The HSS may also store dynamic subscription information,such as the identity of the Mobility Management Entity (MME) to which awireless device is currently attached or registered. The MME and HSScomponents are discussed in detail further below.

As part of the DSA-TPA operations, a DPC may communicate with the HSScomponent to determine the priorities and access rights of the wirelessdevices. The DPC may also update the information stored/maintained bythe HSS component, which may cause the HSS and MME components to storeinconsistent, conflicting or contradictory information. As a result, theDSA system may fail to provide adequate services, especially when theDSA operations are based on tiers and/or for a select subset of thesubscribers.

To overcome these and other limitations, the various embodiments includeDSA components configured to communicate and perform various DSA-HSSuser profile management operations to dynamically add, remove, andmodify subscriber information and profiles so as to allow the HSS andMME component to automatically synchronize their information stores andoperations. This allows the DSA system to better provide DSA servicesbased on tiers and/or for a select subset of the subscribers.

In an embodiment, a HSS component may be configured to detect changes toHSS subscription information (e.g., user profile information) anddetermine whether the changes affect the information managed/stored byan MME component. The HSS may communicate the detected changes to theMME component when the HSS determines that the changes affect the userprofile information managed/stored by the MME. In various embodiments,the HSS may communicate these changes via a changed data communicationmessage or an “Insert Subscriber Data” communication message.

The MME component may be configured to receive communication messagesthat identify the changes to the subscription information (e.g., HSSinformation), and use the information included in the received messagesto add, remove, or modify the MME's stored subscription information oruser profile information. The MME component may then communicate theseupdates, additions, or changes to the HSS component. These operationsallow the HSS and MME components to automatically synchronize theirdatabases, information stores, and operations, which is particularlyimportant when resources are allocated based on tiers and/or for aselect subset of the subscribers.

In addition, the MME component may be configured to perform variousadditional operations to initiate appropriate actions in response to thedetected changes. For example, in an embodiment, the MME component maybe configured to determine whether a wireless device is allowed to roamin its current network in response to receiving communication messagesthat identify the changes to the subscription information (e.g., HSSinformation). The MME component may be further configured to initiate adetach procedure in response to determining that the wireless device isnot allowed to roam in the current network.

As another example, the MME component may be configured to determinewhether a received public data network (PDN) subscription context has arelated active PDN connection in the MME, determine whether a subscribedQoS profile has been modified, determine whether the wireless device isin one of the ECM CONNECTED or ECM-IDLE states, and determine whether anidle state signaling reduction (ISR) function has been activated for thewireless device. The MME component may be further configured to initiate(or cause the HSS component to initiate) a subscribed QoS modificationprocedure/method in response to determining that the subscribed QoSprofile has been modified, the wireless device is in one of the ECMCONNECTED or ECM-IDLE states, and/or that ISR has not been activated. Ina further embodiment, the MME component may be configured to initiate(or cause the HSS component to initiate) the subscribed QoS modificationprocedure/method after the next ECM IDLE to ECM CONNECTED transition inresponse to determining that the wireless device is in the ECM IDLEstate and ISR has been activated.

As is discussed in detail further below, in an embodiment, a lessor DSCmay be configured to send a resources withdrawn message to the DPC inresponse to the lessor DSC determining that a resource submitted forauction should be withdrawn (e.g., due to administrative reasons). TheDPC may receive the resources withdrawn message, and notify a lessee DSCof the resource withdrawal. The lessee DSC may delete a specific CSG idassociated with the withdrawn resource from all affected eNodeBs inlessee network (i.e., that are managed by the lessee DSC). This maytrigger the eNodeB in lessee network to send a configuration updatemessage to the lessee MME, along with a list of currently supported CSGids (where the CSG id associated with the withdrawn resource is nolonger present). In addition the DPC may inform the HSS about removal ofthe CSG id associated with the withdrawn resource. The HSS may beconfigured to send a changed data communication message or an “InsertSubscriber Data” message to the MMEs in lessee and lessor networks inresponse to receiving notification of the CSG membership change forlessee wireless devices.

The various embodiments may include a DSA system that includes a HSScomponent, a MME component, an eNodeB, a DSC, and a DPC. The DPC may becoupled to the DSC, which may be coupled to the eNodeB. The eNodeB maybe coupled to the MME, which may be coupled to the HSS. In addition, invarious embodiments, the DSC and/or DPC may be coupled to the HSS and/orMME.

The HSS may be configured to determine whether subscription information(or HSS information) stored in a memory of the HSS has changed for awireless device. The HSS may determine whether the changes affect userprofile information stored in a user profile repository of the MME inresponse to determining that the HSS information has changed. The HSSmay generate a changed data communication message that includesinformation identifying the changes to the HSS information, and send thegenerated changed data communication message to the MME.

The MME may be configured to receive the changed data communicationmessage, and perform various operations based on the informationincluded in the received changed data communication message. Forexample, the MME may add subscription information (or user profileinformation) included in the received changed data communication messageto the user profile repository. The MME may also use the informationincluded in the received changed data communication message to modify ordelete subscription information (or user profile information) stored inthe user profile repository. In addition, the MME may be configured touse the information included in the received changed data communicationmessage to determine whether a public data network (PDN) subscriptioncontext has a related active PDN connection in the MME, determinewhether a subscribed quality of service (QoS) profile has been modified,and perform subscribed QoS modification operations.

In an embodiment, the MME may be configured to determine whethersubscription information and a mobile management context of a detachedwireless have been deleted, and send a purge communication message tothe HSS via the first communication link in response to determining thatthe subscription data and a mobile management context of a detachedwireless have been deleted. The HSS may be configured to receiving thepurge communication message, and set a purge flag in response toreceiving the purge communication message. That is, the MME componentmay be configured to send a purge message to the HSS component to causethe HSS component to set a “UE Purged for E-UTRAN” flag in response tothe MME determining that the subscription data and mobile management(MM) contexts of a detached wireless have been deleted or removed.

In various embodiments, the DPC and/or DSC components may be configuredto communicate with an HSS component, such as to exchange wirelessdevice subscription information or user profile information. In anembodiment, the DSC component may be configured to request and receiveuser profile, subscription, and DSA-TPA information from the HSS. Forexample, a lessee DSC may be configured to request subscriptioninformation from a lessee HSS in response to receiving a “Bid Won”message from the DPC. The lessee HSS may send the lessee DSCsubscription information that identifies the wireless device subscribersof the lessee network that are to be allowed access to the resources wonby the lessee network (e.g., the resources identified via the “Bid Won”message). The lessee DSC may then communicate with one or more lesseeMMEs associated with the wireless device subscribers (identified by theHSS) to inform the MMEs that those wireless devices are allowed to usethe leased resources.

The various embodiments may also include components configured toperform DSA methods so as to synchronize user profile, subscriptionand/or DSA information stored, managed, or maintained by the HSS and/orMME components. For example, in an embodiment, an HSS component may beconfigured to determine whether HSS information stored in a memory ofthe HSS has changed for a wireless device. The HSS component may thendetermine whether the changes affect user profile information stored ina user profile repository of a mobility management entity (MME). The HSScomponent may also generate a changed data communication message thatincludes information identifying the changes, and send the generatedchanged data communication message to the MME. In an embodiment, the HSScomponent may be configure to generate the changed data communicationmessage in response to determining that the changes affect user profileinformation stored in a user profile repository of the MME.

The MME component may be configured to receive the changed datacommunication message, and add the information included in the receivedchanged data communication message to the user profile repository of theMME. The MME may also use the information included in the receivedmessage to modify the information stored in the user profile repository.In addition, the MME may use the information included in the receivedchanged data communication message to determine whether a public datanetwork (PDN) subscription context has a related active PDN connectionin the MME and/or to determine whether a subscribed quality of service(QoS) profile has been modified. The MME component may be configured toperform subscribed QoS modification operations in response todetermining that the QoS profile has been modified.

The various embodiments may be implemented within a variety ofcommunication systems, examples of which are illustrated in FIGS. 1A-1E.With reference to FIG. 1A, wireless devices 102 may be configured totransmit and receive voice, data, and control signals to and from a basestation 111, which may be a base transceiver station (BTS), NodeB,eNodeB, etc. The base station 111 may communicate with an access gateway113, which may include one or more of a controller, a gateway, a servinggateway (SGW), a packet data network gateway (PGW), an evolved packetdata gateway (ePDG), a packet data serving node (PDSN), a serving GPRSsupport node (SGSN), or any similar component or combinations of thefeatures/functions provided thereof. Since these structures are wellknown and/or discussed in detail further below, certain details havebeen omitted from FIG. 1A in order to focus the descriptions on the mostrelevant features.

The access gateway 113 may be any logical and/or functional componentthat serves as the primary point of entry and exit of wireless devicetraffic and/or connects the wireless devices 102 to their immediateservice provider and/or packet data networks (PDNs). The access gateway113 may forward the voice, data, and control signals to other networkcomponents as user data packets, provide connectivity to external packetdata networks, manage and store contexts (e.g. network internal routinginformation, etc.), and act as an anchor between different technologies(e.g., 3GPP and non-3GPP systems). The access gateway 113 may coordinatethe transmission and reception of data to and from the Internet 105, aswell as the transmission and reception of voice, data and controlinformation to and from an external service network 104, the Internet105, other base stations 111, and to wireless devices 102.

In various embodiments, the base stations 111 and/or access gateway 113may be coupled (e.g., via wired or wireless communication links) to adynamic spectrum arbitrage (DSA) system configured to dynamically managethe availability, allocation, access, and use of various networkresources (e.g., RF spectrum, RF spectrum resources, etc.). The DSAsystem is discussed in detail further below.

FIG. 1B illustrates that wireless devices 102 may be configured to sendand receive voice, data and control signals to and from the servicenetwork 104 (and ultimately the Internet 105) using a variety ofcommunication systems/technologies (e.g., GPRS, UMTS, LTE, cdmaOne,CDMA2000™), any or all of which may be supported by, or used toimplement, the various embodiments.

In the example illustrated in FIG. 1B, long term evolution (LTE) and/orevolved universal terrestrial radio access network (E-UTRAN) datatransmitted from a wireless device 102 is received by an eNodeB 116, andsent to a serving gateway (SGW) 118 located within the core network 120.The eNodeB 116 may send signaling/control information (e.g., informationpertaining to call setup, security, authentication, etc.) to a mobilitymanagement entity (MME) 130. The MME 130 may request user/subscriptioninformation from a home subscriber server (HSS) 132, communicate withother MME components, perform various administrative tasks (e.g., userauthentication, enforcement of roaming restrictions, etc.), select a SGW118, and send authorization and administrative information to the eNodeB116 and/or SGW 118. Upon receiving the authorization information fromthe MME 130 (e.g., an authentication complete indication, an identifierof a selected SGW, etc.), the eNodeB 116 may send data received from thewireless device 102 to a selected SGW 118. The SGW 118 may storeinformation about the received data (e.g., parameters of the IP bearerservice, network internal routing information, etc.) and forward userdata packets to a policy control enforcement function (PCEF) and/orpacket data network gateway (PGW) 128.

FIG. 1B further illustrates that general packet radio service (GPRS)data transmitted from the wireless devices 102 may be received by a basetransceiver station (BTS) 106 and sent to a base station controller(BSC) and/or packet control unit (PCU) component (BSC/PCU) 108. Codedivision multiple access (CDMA) data transmitted from a wireless device102 may be received by a base transceiver station 106 and sent to a basestation controller (BSC) and/or packet control function (PCF) component(BSC/PCF) 110. Universal mobile telecommunications system (UMTS) datatransmitted from a wireless device 102 may be received by a NodeB 112and sent to a radio network controller (RNC) 114.

The BSC/PCU 108, BSC/PCF 110, and RNC 114 components may process theGPRS, CDMA, and UMTS data, respectively, and send the processed data toa component within the core network 120. More specifically, the BSC/PCU108 and RNC 114 units may send the processed data to a serving GPRSsupport node (SGSN) 122, and the BSC/PCF 110 may send the processed datato a packet data serving node (PDSN) and/or high rate packet dataserving gateway (HSGW) component (PDSN/HSGW) 126. The PDSN/HSGW 126 mayact as a connection point between the radio access network and the IPbased PCEF/PGW 128. The SGSN 122 may be responsible for routing the datawithin a particular geographical service area, and send signaling(control plane) information (e.g., information pertaining to call setup,security, authentication, etc.) to an MME 130. The MME 130 may requestuser and subscription information from a home subscriber server (HSS)132, perform various administrative tasks (e.g., user authentication,enforcement of roaming restrictions, etc.), select a SGW 118, and sendadministrative and/or authorization information to the SGSN 122.

The SGSN 122 may send the GPRS/UMTS data to a selected SGW 118 inresponse to receiving authorization information from the MME 130. TheSGW 118 may store information about the data (e.g., parameters of the IPbearer service, network internal routing information, etc.) and forwarduser data packets to the PCEF/PGW 128. The PCEF/PGW 128 may sendsignaling information (control plane) to a policy control rules function(PCRF) 134. The PCRF 134 may access subscriber databases, create a setof policy rules and performs other specialized functions (e.g.,interacts with online/offline charging systems, application functions,etc.). The PCRF 134 may then send the policy rules to the PCEF/PGW 128for enforcement. The PCEF/PGW 128 may implement the policy rules tocontrol the bandwidth, the quality of service (QoS), the characteristicsof the data, and the services being communicated between the servicenetwork 104 and the end users.

In the various embodiments, any or all of the components discussed above(e.g., components 102-134) may be coupled to, or included in, a DSAsystem configured to dynamically manage the availability, allocation,access, and use of telecommunication resources.

FIG. 1C illustrates various logical components and communication linksin an embodiment system 100 that includes an DSA system 142 and aevolved universal terrestrial radio access network (E-UTRAN) 140. In theexample illustrated in FIG. 1C, the DSA system 142 includes a dynamicspectrum controller (DSC) 144 component and a dynamic spectrum policycontroller (DPC) 146 component. The E-UTRAN 140 includes a plurality ofinterconnected eNodeBs 116 coupled to the core network 120 (e.g., via aconnection to an MME, SGW, etc.).

In various embodiments, the DSC 144 may be included in or coupled to theE-UTRAN 140, either as part of its core network 120 or outside of thecore network 120. In an embodiment, the DSC 144 may be coupled directly(e.g., via wired or wireless communication links) to one or more eNodeBs116.

The eNodeBs 116 may be configured to communicate with the DSC 144 viathe Xe interface/reference point. In various embodiments, the Xereference point between DSC and eNodeB 116 may use the DSAAP protocol,TR-069 protocol, and/or TR-192 data model extensions to support listingavailable resources at the eNodeB 116 and notifying the eNodeB 116 ofbid/buy confirmations. The DSC 144 may be configured to communicate withthe DPC 146 via the Xd interface/reference point. The Xd reference pointbetween DSC and DPC may use the DSAAP protocol for dynamic spectrum andresource arbitrage operations. The eNodeBs 116 may be interconnected,and configured to communicate via an X2 interface/reference point, whichmay also use the DSAAP protocol to communicate information. The eNodeBs116 may be configured to communicate with components in the core network120 via the S1 interface. For example, the eNodeBs 116 may be connectedto an MME 130 via the S1-MME interface and to a SGW 118 via the S1-Uinterface. The S1 interface may support a many-to-many relation betweenthe MMEs 130, SGWs 118, and eNodeBs 116. In embodiment, the DPC and/orDSC component may also be configured to communicate with a HSS 132component.

The eNodeBs 116 may be configured to provide user plane (e.g., PDCP,RLC, MAC, PHY) and control plane (RRC) protocol terminations towards thewireless device 102. That is, the eNodeBs 116 may act as a bridge (e.g.,layer 2 bridge) between the wireless devices 102 and the core network120 by serving as the termination point of all radio protocols towardsthe wireless devices 102, and relaying voice (e.g., VoIP, etc.), data,and control signals to network components in the core network 120. TheeNodeBs 116 may also be configured to perform various radio resourcemanagement operations, such as controlling the usage of radiointerfaces, allocating resources based on requests, prioritizing andscheduling traffic according to various quality of service (QoS)requirements, monitoring the usage of network resources, etc. Inaddition, the eNodeBs 116 may be configured to collect radio signallevel measurements, analyze the collected radio signal levelmeasurements, and handover wireless devices 102 (or connections to themobile devices) to another base station (e.g., a second eNodeB) based onthe results of the analysis.

The DSC 144 and DPC 146 may be functional components configured tomanage the dynamic spectrum arbitrage process for sharing radiofrequency and other network resources between different E-UTRANs 140.For example, the DPC 146 component may be configured to manage the DSAoperations and interactions between multiple E-UTRAN networks bycommunicating with DSCs 144 in the E-UTRAN network.

FIG. 1D illustrates various logical and functional components that maybe included in a communication system 101 that suitable for use inperforming DSA operations in accordance with various embodiments. In theexample illustrated in FIG. 1D, the communication system 101 includes aneNodeB 116, a DSC 144, a DPC 146, an MME 130, a SGW 118, and a PGW 128.

The eNodeB 116 may include a DSC application protocol and congestionmonitoring module 150, an inter-cell radio resource management (RRM)module 151, a radio bearer (RB) control module 152, a connectionmobility control module 153, a radio admission control module 154, aneNodeB measurement configuration and provision module 155, and a dynamicresource allocation module 156. Each of these modules 150-156 may beimplemented in hardware, in software, or in a combination of hardwareand software.

In addition, the eNodeB 116 may include various protocol layers,including a radio resource control (RRC) layer 157, a packet dataconvergence protocol (PDCP) layer 158, a radio link control (RLC) layer159, a medium access control (MAC) layer 160, and a physical (PHY) layer161. In each of these protocol layers, various hardware and/or softwarecomponents may implement functionality that is commensurate withresponsibilities assigned to that layer. For example, data streams maybe received in the physical layer 161, which may include a radioreceiver, buffers, and processing components that perform the operationsof demodulating, recognizing symbols within the radio frequency (RF)signal, and performing other operations for extracting raw data from thereceived RF signal.

The DSC 144 may include an eNodeB geographic boundary management module162, an eNodeB resource and congestion management module 163, a streamcontrol transmission protocol (SCTP) module 164, a Layer-2 (L2) buffermodule 165, and a Layer-1 (L1) buffer module 166. The DPC 146 mayinclude an eNodeB resource bid management module 167, an inter-DSCcommunication module 168, SCTP/DIAMETER module 169, an L2 buffer module170, and a L1 buffer module 171. The MME 130 may include a non-accessstratum (NAS) security module 172, and idle state mobility handlingmodule 173, and an evolved packet system (EPS) bearer control module174. The SGW 118 may include a mobility anchoring module 176. The PGW128 may include a UE IP address allocation module 178 and a packetfiltering module 179. Each of these modules 162-179 may be implementedin hardware, in software, or in a combination of hardware and software.

The eNodeB 116 may be configured to communicate with the SGW 118 and/orMME 130 via the S1 interface/protocol. The eNodeB 116 may also beconfigured to communicate with the DSC 144 via the Xeinterface/protocol. The DSC 144 may be configured to communicate withthe DPC 146 via the Xd interface/protocol.

The eNodeB 116 may be configured to perform various operations (e.g.,via modules/layers 150-161) to provide various functions, includingfunctions for radio resource management, such as radio bearer control,radio admission control, connection mobility control, dynamic allocationof resources to wireless devices 102 in both uplink and downlink(scheduling), etc. These functions may also include IP headercompression and encryption of user data stream, selection of an MME atUE attachment when no routing to an MME 130 can be determined from theinformation provided by the UE, routing of user plane data towards SGW118, scheduling and transmission of paging messages (originated from theMME), scheduling and transmission of broadcast information (originatedfrom the MME), measurement and measurement reporting configuration formobility and scheduling, scheduling and transmission of public warningsystem (e.g., earthquake and tsunami warning system, commercial mobilealert service, etc.) messages (originated from the MME), closedsubscriber group (CSG) handling, and transport level packet marking inthe uplink. In an embodiment, the eNodeB 116 may be a donor eNodeB(DeNB) that is configured to perform various operations to provideadditional functions, such as an S1/X2 proxy functionality, S11termination, and/or SGW/PGW functionality for supporting relay nodes(RNs).

The MME 130 may be configured to perform various operations (e.g., viamodules 172-175) to provide various functions, including non-accessstratum (NAS) signaling, NAS signaling security, access stratum (AS)security control, inter-CN node signaling for mobility between 3GPPaccess networks, idle mode UE reach-ability (including control andexecution of paging retransmission), tracking area list management(e.g., for a wireless device in idle and active mode), PGW and SGWselection, MME selection for handovers with MME change, SGSN selectionfor handovers to 2G or 3G 3GPP access networks, roaming, authentication,bearer management functions including dedicated bearer establishment,support for public warning system (e.g., earthquake and tsunami warningsystem, commercial mobile alert service, etc.) message transmission, andperforming paging optimization. The MME module may also communicatevarious device state and attach/detach status information to the DSC. Inan embodiment, the MME 130 may be configured to not filter pagingmassages based on the CSG IDs towards macro eNodeBs.

The SGW 118 may be configured to perform various operations (e.g., viamodule 176) to provide various functions, including mobility anchoring(e.g., for inter-3GPP mobility), serving as a local mobility anchorpoint for inter-eNodeB handovers, E-UTRAN idle mode downlink packetbuffering, initiation of network triggered service request procedures,lawful interception, packet routing and forwarding, transport levelpacket marking in the uplink (UL) and the downlink (DL), accounting onuser and QoS class identifier (QCI) granularity for inter-operatorcharging, uplink (UL) and the downlink (DL) charging (e.g., per device,PDN, and/or QCI), etc.

The PGW 128 may be configured to perform various operations (e.g., viamodules 178-179) to provide various functions, including per-user basedpacket filtering (by e.g. deep packet inspection), lawful interception,UE IP address allocation, transport level packet marking in the uplinkand the downlink, UL and DL service level charging, gating and rateenforcement, DL rate enforcement based on APN-aggregate maximum bit rate(AMBR), etc.

The DSC 144 may be configured to perform various operations (e.g., viamodules 162-166) to provide various functions, including managingresource arbitration operations within a network (e.g., PLMN), trackingnetwork resource listings, tracking current bids in progress, trackingexecuted bids, and tracking bid specific closed subscriber group (CSG)identifiers (CSG-IDs) for mobility management of lessee wireless devices102 in lessor networks. The DSC 144 may be configured to handoverwireless devices 102 from lessee network to lessor network (i.e.,perform handins), and handover wireless devices 102 from lessor networkback to lessee network (i.e., perform backoff).

The DSC 144 may also be configured to track congestion states ofeNodeBs, select target eNodeBs for handovers, and manage traffic onlessor eNodeBs. The DSC 144 may be configured to offload users based onconfigured policies (e.g. offload lower priority users, offload higherpriority users, offload users with specific QoS, etc.) from lesseenetworks to other less loaded eNodeBs 116 within a lessor network. TheDSC 144 may also perform backoff operations to handover a wirelessdevice 102 from lessor network back to the lessee network. The DSC 144may also be configured to monitor, manage, and/or maintain historiccongestion information that is collected or received from one or moreeNodeBs in the system.

The DPC 146 may be configured to perform various operations (e.g., viamodules 167-171) to provide various functions, including functioning asa resource arbitrage broker between the DSCs 144 of lessor and lesseenetworks (e.g., PLMNs), listing resources from various lessor networksfor auction, and managing the auction process. The DPC 146 may beconfigured to send notifications of outbid, bid win, bid cancel and bidwithdrawal and bid expiry to DSCs 144, install bid specific chargingrules in the online and/or offline charging systems of lessee and lessornetworks, and coordinate resource usage between DSCs 144 by acting asgateway between lessee and lessor DSCs 144.

FIG. 1E illustrates network components and information flows in anexample communication system 103 that includes two E-UTRANs 140 a, 140 binterconnected by a DPC 146 configured to manage DSA operations andinteractions. In the example illustrated in FIG. 1E, each E-UTRAN 140 a,140 b includes an eNodeB 116 a, 116 b that is outside of its corenetwork 120 a, 120 b, and a DSC 144 a, 144 b that is inside of the corenetwork 120 a, 120 b.

The DSCs 144 a, 144 b may be configured to communicate with the DPC 146via Xd interface. The DSCs 144 a, 144 b may also be connected, directlyor indirectly, to various network components in their respective corenetworks 120 a, 120 b, such as a PCRF 134, HSS 132 and a PCEF/PGW 128(not illustrated in FIG. 1E). In an embodiment, one or more of the DSCs144 a, 144 b may be connected directly to one or more of the eNodeBs 116a, 116 b.

In addition to the above-mentioned connections and communication links,the system 103 may include additional connections/links to accommodatedata flows and communications between components in different E-UTRANs(e.g., E-UTRANS 140 a and 140 b). For example, the system 103 mayinclude a connection/communication link between an eNodeB 116 b in thesecond E-UTRAN 140 b to an SGW 118 in the first E-UTRAN 140 a. Asanother example, the system 103 may include a connection/communicationlink between a SGW 118 in the second E-UTRAN 140 b to a PGW 128 in thefirst E-UTRAN 140 a. To focus the discussion of the relevantembodiments, these additional components, connections, and communicationlinks are not illustrated in FIG. 1E.

As is discussed in detail further below, the DSCs 144 a, 144 b may beconfigured to send information regarding the availability of spectrumresources (e.g., information received from an eNodeB, PCRF, PCEF, PGW,etc.) to the DPC 146. This information may include data relating tocurrent and expected future usage and/or capacity of each network orsub-network. The DPC 146 may be configured to receive and use suchinformation to intelligently allocate, transfer, manage, coordinate, orlease the available resources of the first E-UTRAN 140 a to the secondE-UTRAN 140 b, and vice versa.

For example, the DPC 146 may be configured to coordinate the allocationof spectrum resources to the second E-UTRAN 140 b (i.e., lessee network)from the E-UTRAN 140 a (i.e., lessor network) as part of the dynamicspectrum arbitrage operations. Such operations may allow a wirelessdevice 102 that is wirelessly connected to the eNodeB 116 b in thesecond E-UTRAN 140 b via a communication link 143 to be handed off to aneNodeB 116 a in the first E-UTRAN 140 a so that it may use the allocatedspectrum resources of the first E-UTRAN 140 a. As part of this handoffprocedure, the wireless device 102 may establish a new connection 141 tothe eNodeB 116 a in the first E-UTRAN 140 a, terminate the wirelessconnection 143 to the original eNodeB 116 b, and use the allocatedresources of the first E-UTRAN 140 a as if they are included in thesecond E-UTRAN 140 b. The DSA operations may be performed so that thefirst DSC 144 a is a lessor DSC for a first resource/period of time, anda lessee DSC for a second resource or another period of time.

In an embodiment, the DSA and/or handoff operations may be performed sothat the wireless device 102 maintains a data connection to (or a dataconnection that is managed by) the original network after it is handedoff. For example, DSA and/or handoff operations may be performed so thatthe wireless device 102 maintains a dataflow connection to a PGW 128 inthe second E-UTRAN 140 b after being handed off to the eNodeB 116 a inthe first E-UTRAN 140 a.

FIG. 2A illustrates an example DSA method 200 of allocating resources inaccordance with an embodiment. Method 200 may be performed by aprocessing core in a DPC 146 component (e.g., server computing device,etc.).

In block 202, the DPC 146 may establish a first communication link to afirst DSC 144 a in a first communication network (e.g., E-UTRAN, etc.).In block 204, the DPC 146 may establish a second communication link to asecond DSC 144 b in a second communication network. In block 206, theDPC 146 may determine whether radio frequency (RF) spectrum resourcesare available for allocation within the second communication network.This may be accomplished by using the DSAAP protocol to communicate witha DSC 144 in the second communication network via the secondcommunication link, which may be a wired or wireless communication link.In block 208, the DPC 146 may determine the amount of RF spectrumresources that are available for allocation. In block 210, the DPC 146may perform various operations to allocate all or a portion of theavailable RF resources of the second communication network for accessand use by wireless devices 102 in the first communication network.

In block 212, the DPC 146 may send a communication message to the firstDSC 144 a (e.g., by using the DSAAP protocol) to inform the firstcommunication network that the use of the allocated RF spectrumresources may begin. In block 214, the DPC 146 may record a transactionin a transaction database identifying an amount of RF spectrum resourcesallocated for use by the first communication network.

In block 216, the DPC 146 may receive a communication message from thesecond DSC 144 b that includes information indicating that the allocatedresources have been consumed and/or requesting that the allocatedresources be released. In block 218, the DPC 146 may send a resourceconsumed/release message to the first DSC 144 a to cause the firstnetwork to terminate its use of the allocated resources.

FIG. 2B illustrates example information flows between a DPC 146 and aplurality of DSCs 144 a-d when performing another embodiment DSA method250 to allocate resources. In the description below, the DSA method 250is discussed from the perspective of the DPC 146 component, and may beperformed by a processing core in the DPC 146. However, it should beunderstood that the DSA method 250 may be performed by processing coresin a DPC 146 component, processing cores in DSC 144 a-d components, or acombination thereof. In addition, it should be understood that all theinteractions and communications between the DPC 146 and the othercomponents may be accomplished by DSAAP components and/or using theDSAAP protocol. As such, all such interactions and communications may beincluded in the DSAAP protocol.

In operation 252, a processing core in a DPC 146 component may receive a“request for resources” communication message from a first DSC 144 acomponent in a first network (e.g., E-UTRAN, etc.). It should beunderstood that the “request for resources” communication message andall other communication messages discussed in this application may beDSAAP messages.

The “request for resources” communication message may includeinformation suitable for informing the DPC 146 that the first network isinterested in purchasing, leasing, accessing, and/or using resourcesfrom other networks. The “request for resources” communication messagemay also include information suitable for identifying the types and/oramounts of resources (e.g., RF spectrum resources, etc.) that arerequested by the first network, the types and capabilities of thewireless devices 102 to which the requested resources will be allocated,and other similar information.

In operations 254, 256, and 258 the DPC 146 may generate and send a“resource inquiry” communication message to each of a second DSC 144 bcomponent in a second network, a third DSC 144 c component in a thirdnetwork, and a fourth DSC 144 d component in a fourth network,respectively. The DPC 146 may be configured to generate the “resourceinquiry” communication messages to include various component, device,and resource requirements, criteria, and information. For example, theDPC 146 may generate a “resource inquiry” communication message toinclude information identifying the types, capabilities, and geographiccriteria of user wireless devices 102 in the first network (and othernetworks) to which resources are to be allocated. The geographiccriteria may include a geographic location, a geographic polygon, and/orlicense area for a user wireless device 102 to which resources will beallocated.

In operations 260 and 262, the DPC 146 may receive “resource inquiryresponse” communication messages from the second and third DSCs 144 b,144 c. These “resource inquiry response” communication messages mayinclude information identifying the availability of excess resourcesthat comply with the requirements/criteria included in the resourceinquiry messages. In operation 264, the DPC 146 may receive another“resource inquiry response” communication message from the fourth DSC144 d. This “resource inquiry response” communication messages mayinclude information indicating that the fourth network does not includeresources that meet the requested requirements/criteria.

In an embodiment, as part of operations 260-264, the DPC 146 may updatea database record to identify the second and third networks as havingresources available for allocation and/or to identify the fourth networkas not including such resources.

In operation 266, the DPC 146 may generate and send a “resourceavailability” communication message to a plurality of DSCs in aplurality of networks, including the first DSC 144 a in the firstnetwork. The DPC 146 may be configured to generate the “resourceavailability” communication message to include information that issuitable for informing the networks that resources are available forallocation. In an embodiment, the DPC 146 may be configured to informthe networks that resources are available for allocation by broadcastinga communication signal that includes information suitable for informingthe networks that resources are available for allocation via auctionand/or an auction start time for the auction.

In operation 268, the DPC 146 may receive a “resource reservationrequest” communication message from the first DSC 144 a. The received“resource reservation request” communication message may includeinformation suitable for informing the DPC 146 that the first networkintends to participate in the auction and/or bid on at least a portionof the available resources.

In operations 270 and 272, the DPC 146 may send the “resourcereservation request” communication message to the second and third DSCs144 b, 144 c, respectively. The “resource reservation request”communication message may include information suitable for causing thesecond and third DSCs 144 b, 144 c to reserve all or a portion of theiravailable resources for allocation and use by other networks.

In operations 274 and 276, the DPC 146 may receive a “resourcereservation response” communication message from each of the second andthird DSCs 144 b, 144 c. The “resource reservation response” messagesmay include information suitable for informing the DPC 146 that therequested resources that have been reserved and/or information suitablefor identifying the reserved resources.

Optionally, in operation block 278, the DPC 146 may pool the reservedresources for allocation and use by wireless devices 102 in othernetworks (e.g., the first network). For example, the DPC 146 may combinea block of spectrum reserved in the second network with a block ofspectrum reserved in the third network. As another example, the DPC 146may pool the resources available in the first and fourth channels of ablock of spectrum reserved in the second network.

In operation 280, the DPC 146 may receive “resource bid” communicationmessages from a plurality of networks, including from the first DSC 144a in the first network. Each “resource bid” communication message mayinclude a bid or offer for accessing, using, leasing, and/or purchasinga resource, as well as other related bid information (e.g., price,requested allocation/access methods, etc.). As part of operation 280,the DPC 146 may determine whether the received resource bids comply withthe policies and rules of the DSA system and/or with requirements setforth by the networks offering the resources for allocation (e.g., meetthe minimum asking price, etc.).

In operation 282, the DPC 146 may accept the bid/offer from the firstnetwork in response to determining that the resource bid received fromthe first network complies with the policies/rules of the DSA system andwith requirements set forth by the resource offering network (e.g.,offers a monetary amount for the use of all or a portion of theresources in the pool of available resources that is greater than orequal to a minimum amount specified by the second network). Also inoperation 282, the DPC 146 may generate and send a “bid acceptance”communication message to the first DSC 144 a.

In operation 284, the DPC 146 may allocate the resources of the secondnetwork for access and used by wireless devices 102 in the first networkby sending an “assign resources request” communication message to thesecond DSC 144 b. That is, in operation 284, the DPC may determine thatthe portion of the resources (e.g., in the pool of available resources)won by the first DSC 144 a are fully available via the second network,and in response, only send the assign resources request message to thesecond network.

In operation 286, the DPC 146 may receive a “resources allocated”communication message from the second DSC 144 b. In operation 288, theDPC 146 may send the “resources allocated” communication message to thefirst DSC 144 a to inform the first network that the resources have beenallocated for access and used by its wireless devices 102 and/or thatthe use of the allocated resources may begin. In operation block 290,the DPC 146 may record a transaction in a transaction databaseidentifying these resources as being allocated for access and use by thefirst network.

In operation 292, the DPC 146 may receive a “release resources”communication message from the second DSC 144 b that includesinformation indicating that the allocated resources have been consumedand/or information suitable for requesting that the allocated resourcesbe released. In operation 294, the DPC 146 may send a resourceconsumed/release message to the first DSC 144 a to cause the firstnetwork to terminate its use of the allocated resources.

FIGS. 3-7 illustrate an embodiment DSA method 300 for allocating andaccessing resources in a communication system that includes a DPC 146component, two DSC 144 a, 144 b components, and wireless devices 102.All or portions of DSA method 300 may be performed by processing coresin a DPC 146, DSCs 144 a-b, and/or wireless device 102. In the variousembodiments, any of all of the interactions and communications betweenthe components 146, 144 a, 144 b, and 102 may be accomplished orfacilitated by DSAAP components and/or using the DSAAP protocol. Assuch, all such interactions and communications may be included in theDSAAP protocol.

With reference to FIG. 3, in block 302, a first DSC 144 a in a firstnetwork may monitor user traffic (e.g., call and data traffic, etc.) ascompared to the total spectrum resources available to the first network.In block 304, the first DSC 144 a may generate a resource status reportbased on a result of its monitoring, record/store the resource statusreport in memory, and send a resource status report to the DPC 146 via aresources status report communication message. In determination block306, the first DSC 144 a may determine, based on the received resourcestatus reports, whether additional resources are required (and/orwhether there is a high probability that additional resources will berequired in the near future) to provide adequate service to the existingwireless devices 102 in the first network. In response to determiningthat additional resources are required (i.e., determination block306=“Yes”), in block 308, the first DSC 144 a may send a “request forresources” communication message to the DPC 146. In response todetermining that additional resources are not required (i.e.,determination block 306=“No”), the first DSC 144 a may continuemonitoring user traffic and/or perform other DSC operations in block302.

In block 310, a second DSC 144 b in a second network may monitor usertraffic as compared to the total spectrum resources available to thesecond network, generate resource status reports, and/or perform any orall of the DSC operations discussed in this application. Indetermination block 312, the second DSC 144 b may determine whetherthere is an excess amount of resources available in the second network.In response to determining that there are no excess resources availablein the second network (i.e., determination block 312=“No”), in block310, the second DSC 144 b may continue monitoring user traffic and/orperforming other DSC operations.

In response to determining that there is an excess amount of resourcesavailable in the second network (i.e., determination block 312=“Yes”),in block 314, the second DSC 144 b may mark, designate, or allocate allor portions of its excess resources for access and use by other networks(e.g., the first network, etc.). In block 316, the second DSC 144 b maygenerate a resource allocation report, and send the generated resourceallocation report to the DPC 146 (e.g., via a resource communicationmessage). The DSC 144 b may be configured to generate the resourceallocation report to include information identifying the resources (orportions or amounts of resources) that are available for allocationand/or that have been marked, designated, or allocated by the secondnetwork.

In block 320, the DPC 146 may receive various resource status andallocation reports from DSCs 144 in many different networks, includingthe first and second DSCs 144 a, 144 b in the first and second networks.These reports may include information identifying variouscharacteristics, criteria, requirements, and conditions of the networksand their components, such as the ratio of the detected user traffic tothe total available spectrum resources, the amount of resources that arerequired by a network, the amount of resources that are available forallocation in a network, the types and capabilities of the wirelessdevices 102 that will use the allocated resources, system requirementsthat must be met before the wireless devices 102 access the allocatedresources, network rules and policies with respect to access and use ofresources, and other similar information.

In block 322, the DPC 146 may store the received reports (e.g., resourcestatus reports, resource allocation reports, etc.) in memory (e.g., anon-volatile memory). In block 324, the DPC 146 may receive a requestfor resources from DSCs 144 in different networks, including the firstDSC 144 a in the first network. In block 326, the DPC 146 may use thereceived/stored information (e.g., information received in requests forresources, resource allocation reports, resource status reports, etc.)to identify and select the most suitable/best available network fromwhich the first network may lease or purchase additional resources. Inthe example illustrated in FIG. 3, the DPC 146 identifies and selectsthe second network as the most suitable network to provide resources tothe first network.

In block 328, the DPC 146 may send a resource inquiry communicationmessage to the second DSC 1144 b. In block 330, the second DSC 1144 bmay receive the resource inquiry communication message. In block 332,the second DSC 1144 b may determine the availability, amounts, and/orquantity of the excess resources that are marked, designated, orallocated by the second network. In block 334, the second DSC 1144 b maygenerate and send a “resource inquiry response” communication message tothe DPC 146. The second DSC 1144 b may generate resource inquiryresponse to include information suitable for use in identifying theavailability and quantity of the resources that are marked, designated,or allocated for access and use by other networks (e.g., the firstnetwork). In block 336, the DPC 146 may receive the “resources inquiryresponse” communication message from the second DSC 1144 b, and inresponse, perform the operations of determination block 400 illustratedin FIG. 4.

With reference to FIG. 4, in determination block 400, the DPC 146 maydetermine whether resources are available based on the data (e.g.,resources inquiry response message) received from the second DSC 144 bin the second network. For example, the DPC 146 may determine that theidentified resources are not available in response to determining thatall or a portion of the resources were purchased or won by other biddersbefore they were reserved.

In response to determining that the resources are not available (i.e.,determination block 400=“No”), in block 402, the DPC 146 may send a “noresources available” communication message to the first DSC 144 a in thefirst network. In block 404, the first DSC 144 a may receive the “noresources available” communication message. In block 406, the first DSC144 a may search (e.g., via the DPC 146) for other available resources,request resources from a different network, request different resources,terminate connections or communication sessions with users to free-upresources, or perform other similar operations to manage network trafficand congestion in the first network.

In response to determining that the resources are available (i.e.,determination block 400=“Yes”), in block 408, the DPC 146 may send a“resources available” communication message to the first DSC 144 a. Theresources available message may include information that may be used bythe first DSC 144 a to determine the quality and quantity of resourcesin the second network that may be used by wireless devices 102 in thefirst network.

In block 410, the first DSC 144 a may receive the resources availablecommunication message sent from the DPC 146. In block 412, the first DSC144 a may determine the amount/quantity of resources that the firstnetwork requires and/or will attempt to acquire, and send this and otherresource information to the DPC 146 in a “request resources”communication message.

In block 414, the DPC 146 may receive the “request resources” messagefrom the first DSC 144 a. In block 416, the DPC 146 may use informationincluded in received message to generate and send a “reserve resourcesrequest” communication message to the second DSC 144 b in the secondnetwork.

In block 418, the second DSC 144 b may receive the “reserve resourcerequest” message from the DPC 146. In block 420, the second DSC 144 bmay use the information included in the received “reserve resourcesrequest” message to reserve the requested quantity of allocatedresources for access and use by components in other networks. In block422, the second DSC 144 b may send a “resource reserved” communicationmessage to the DPC 146 to confirm that the requested quantity ofresources has been reserved and/or to identify the reserved resources.

In block 424, the DPC 146 may receive the “resource reserved”communication message from the second DSC 144 b. In block 426, the DPC146 may offer the reserved resources for auction and/or begin acceptingresource bids on the reserved resources.

FIG. 5 illustrates a bidding procedure of the DSA method 300 that may beperformed after the DPC 146 offers the reserved resources for auctionand/or begins accepting resource bids on the reserved resources (e.g.,after performing the operations of block 426 illustrated in FIG. 4).

With reference to FIG. 5, in block 500, the first DSC 144 a in the firstnetwork may negotiate access to the reserved resources of second networkby sending a resource bid (e.g., via a communication message) to the DPC146. In block 502, the DPC 146 may receive the resource bid from thefirst DSC 144 a.

In determination block 504, the DPC 146 may determine whether thereceived resource bid is to be accepted, which may be accomplished bydetermining whether the resource bid complies with the policies andrules of the DSA system and the requirements of the second network(e.g., is greater than a minimum amount, etc.). In response todetermining that the resource bid received from the first DSC 144 a isto be accepted (i.e., determination block 504=“Yes”), in block 506, theDPC 146 may send an “accept bid” communication message to the first DSC144 a. In block 508, the first DSC 144 a may receive the “accept bid”message and wait to receive resource access instructions. In block 510,the DPC 146 may send an “assign resources” communication message to thesecond DSC 144 b in the second network.

In block 512, the second DSC 144 b may receive the “assign resources”communication message from the DPC 146. In block 514, the second DSC 144b may use the information included in the received “assign resources”message to assign all or portions of its reserved resources for accessand use by components in the first network. In block 516, the second DSC144 b may generate a “resources access” communication message thatincludes information (e.g., access parameters, etc.) that may be used bya wireless device 102 (i.e., in the first network) to access theassigned resources, and the send the “resources access” message to theDPC 146. In block 518, the second DSC 144 b may perform variousoperations to prepare for establishing a communication session/link towireless device 102 in the first network, such as by configuring orpreparing to receive a voice or data call.

In block 522, the DPC 146 may receive the “resources access”communication message from the second DSC 144 b, and relay the resourcesaccess message to the first DSC 144 a. In block 524, the first DSC 144 amay receive the “resources access” message from the DPC 146. Thereceived “resource access” message may include access parameters thatmay be used by the wireless devices 102 to access the allocatedresources of the second network. In block 526, the first DSC 144 a maysend access parameters to wireless devices 102 that have communicationsessions with the first network and/or to the wireless devices 102 thatthe first network has designated/marked for migration to other networks.

In block 528, the wireless devices 102 may receive the access parametersof second network from the first DSC 144 a. In blocks 530 and 520, thewireless devices 102 and/or second DSC 142 b may perform variousoperations to establish a communication session/link between thewireless devices 102 and the second network. The second DSC 144 b maythen perform the operations of block 700 illustrated in FIG. 7 anddiscussed further below.

As mentioned above, in determination block 504, the DPC 146 maydetermine whether the resource bid received from the first DSC 144 a isto be accepted. In response to determining that the resource bidreceived from the first DSC 144 a is not to be accepted (i.e.,determination block 504=“No”), the DPC 146 may perform the operations ofblock 600 illustrated in FIG. 6.

With reference to FIG. 6, in block 600, the DPC 146 may send a “rejectedbid” communication message to the first DSC 144 a. In block 602, thefirst DSC 144 a may receive the “rejected bid” message from the DPC 146.In determination block 604, the first DSC 144 a may determine whetherthe first network will/should rebid for the resources. In response todetermining that the first network will/should rebid for the resources(i.e., determination block 604=“Yes”), in block 606, the first DSC 144 amay send a new resource bid (e.g., in a resource bid communicationmessage) to the DPC 146.

In block 608, the DPC 146 may receive the new resource bid (or rebid)from the first DSC 144 a. In determination block 610, the DPC 146 maydetermine whether to accept the new resource bid, such as by determiningwhether the new resource bid complies with the policies and rules of theDSA system and the requirements of the second network. In response todetermining that the new resource bid is to be accepted (i.e.,determination block 610=“Yes”), the DPC 146 may perform the operationsof block 506 illustrated in FIG. 5. In response to determining that thenew resource bid is to not be accepted (i.e., determination block610=“No”), the DPC 146 may perform the operations of block 600.

In response to determining that the first network should rebid for theresources (i.e., determination block 604=“No”), in block 612, the firstDSC 144 a may send a “cancel resource request” communication message tothe DPC 146. In block 614, the DPC 146 may receive the “cancel resourcerequest” message from the first DSC 144 a. In block 616, the DPC 146 maysend a “release of resources” communication message to the second DSC144 b.

In block 618, the second DSC 144 b may receive the “release ofresources” message from the DPC 146. In block 620, the second DSC 144 bmay release the reserved resources so that they may be used by othernetworks. The second DSC 144 b may then report the status of theallocated resources to DPC 146, which may be accomplished by performingthe operations of block 316, which is illustrated in FIG. 3 anddiscussed above.

FIG. 7 illustrates settlement procedure of the DSA method 300 that maybe performed after second network provides access to the secondary userwireless devices 102 in the first network (i.e., after performing theoperations of block 520 illustrated in FIG. 5).

In block 700, the second DSC 144 b may send invoices and paymentinstructions relating to the use of allocated resources by the firstnetwork to the DPC 146. In block 704, the DPC 146 may relay the receivedinvoice and payment instructions to the first DSC 144 a. In block 706,the first DSC 144 a may receive the invoices and payment instructions,and settle the charges with the second network in block 718.

Optionally or alternatively, in block 708, the second DSC 144 b may sendusage parameters and payment instructions to the DPC 146. In block 710,the DPC 146 may receive the usage parameters and payment instructionsfrom the second DSC 144 b. In block 712, the DPC 146 may create aninvoice for the access and use of the resources. In block 714, the DPC146 may send the invoice to the first DSC 144 a in the first network. Inblock 716, the first DSC 144 a may receive the invoice and paymentinstructions, and perform various operations to settle the charges withsecond network in block 718.

In the various embodiments, the DPC 146 and DSC 144 components may beconfigured to communicate via an interface, which may be implemented in,or provided via, a dynamic spectrum arbitrage application part (DSAAP)protocol/module/component that is defined over the Xe and/or Xdreference points. The DSAAP may allow, facilitate, support, or augmentcommunications between the DPC 146 and DSC 144 so as to improve theefficiency and speed of the DSA system and telecommunication network. Invarious embodiments, all or portions of the DSAAP module/component maybe included in a DPC 146 component, a DSC 144 component, in a componentthat is independent of the DPC 146 and DSC 144 components, or anycombination thereof. The DSAAP module/component may allow these andother DSA components to communicate information using the DSAAPprotocol.

For example, the DSAAP may allow the DPC 146 and DSC 144 components tocommunicate specific information and/or perform operations that togetherprovide various functions, including a DSC registration function,resource availability advertisement function, bidding and allocation ofresources functions, handing off lessee users to lessor networkfunction, backoff from lessor networks function, error handling function(e.g., reporting of general error situations for which function specificerror messages are not defined, etc.), DSC de-registration function,error indication function, DSC bidding success and failure indicationfunctions, and DSC resource allocation withdrawal function. In variousembodiments, these functions may be provided, implemented, oraccomplished by configuring the DPC 146 and/or DSC 144 components toperform one or a combination of the DSAAP methods discussed below withreference to FIGS. 8A-17B. Using the DSAAP protocol and performing theDSAAP methods may include communicating via one or more DSAAP messages.

In various embodiments, the DSAAP messages used to communicateinformation between the DSC 144 and DPC 146 may include a DSC REGISTERREQUEST message, DSC REGISTER ACCEPT message, DSC REGISTER REJECTmessage, DSC DE-REGISTER message, DSC RESOURCE REGISTER REQUEST message,DSC RESOURCE REGISTER ACCEPT message, DSC RESOURCE REGISTER REJECTmessage, AVAILABLE BIDS REQUEST message, AVAILABLE BIDS RESPONSEmessage, AVAILABLE BIDS REJECT message, DSC BID REQUEST message, DSC BIDACCEPT message, DSC BID REJECT message, DSC BID OUTBID message, DSC BIDWON message, DSC BID LOST message, DSC BID CANCELLED message, DSC BUYREQUEST message, DSC BUY ACCEPT message, DSC BUY REJECT message, DSCRESOURCES ALLOCATED message, DSC RESOURCES WITHDRAWN message, and/or DSCBACKOFF COMMAND message. Each of these messages may include, or may beassociated with, criticality information, presence information, rangeinformation, and assigned criticality information. These messages andtheir contents are discussed in detail further below.

In various embodiments, the DSAAP methods may be performed in a DSAsystem that includes a first DSC server in a first telecommunicationnetwork (e.g., a lessee network), a second DSC server in secondtelecommunication network (e.g., a lessor network), and a DPC serverthat is outside of the first and second telecommunication networks. Thefirst DSC may include first DSC processor coupled to the DPC via a firstcommunication link, and the second DSC may include a second DSCprocessor coupled to the DPC via a second communication link. The secondDSC may be coupled to an eNodeB in the second telecommunication networkvia third communication link. The first and second communication linksmay be defined over the Xd interface, and the third communication linkis defined over the Xe interface.

FIGS. 8A through 8C illustrate an embodiment DSAAP registration method800 for registering a DSC 144 component with a DPC 146 so as to allowthe DPC 146 to provide various services to the DSC 144 (e.g.,advertising a lessor DSC's 144 resources for bidding, allowing a lesseeDSC 144 to bid for resources provided by other networks, etc.). In theexamples illustrated in FIGS. 8A through 8C, the DSAAP registrationmethod 800 is performed by processing cores in a DPC 146 component and aDSC 144 component, each of which may include all or portions of a DSAAPmodule/component. The operations DSAAP registration method 800 may beperformed after, or in response to the DSC 144 or DPC 146 detectingthat, an XE signaling transport or communication link has beenestablished.

In operation 802 illustrated in FIGS. 8A through 8C, the DSC 144 mayinitiate DSAAP registration method 800 by generating and sending a DSCREGISTER REQUEST message to the DPC 146. In an embodiment, the DSC 144may be configured to generate and/or send the DSC REGISTER REQUESTmessage in response to determining that it requires services from theDPC 146. For example, the DSC 144 may be configured to generate the DSCREGISTER REQUEST message in response to determining that itscorresponding network (i.e., the network represented by the DSC)includes excess resources that may be allocated to other networks. Asanother example, the DSC 144 may be configured to generate the DSCREGISTER REQUEST message in response to determining that its networkrequires additional resources to provide adequate service to itsexisting wireless devices 102 in view of the current or expected futureuser traffic, network congestion, etc.

In various embodiments, the DSC 144 may be configured to generate theDSC REGISTER REQUEST message to include any or all of a message typeinformation element (IE), a message ID IE, a DSC identity IE, a DSCInternet protocol (IP) address IE, a DSC type IE, a DSC PLMN-ID IE, PLMNtype IE, and DSC resource update timer IE. The DSC PLMN-ID IE mayinclude a PLMN ID that is suitable for use in identifying the network(e.g., E-UTRAN) that is associated with, or represented by, the DSC 144.The PLMN type IE may include information that is suitable for use indetermining the type of network (e.g., public safety, commercial, etc.)that is represented by the DSC 144. The DSC IP address IE may includethe IP address of a DSC 144 that is responsible for managing,maintaining, or providing the XE interface of the DSAAP.

In operation block 804 illustrated in FIGS. 8A and 8B, the DPC 146 mayperform various registration operations (i.e., authenticating the DSC,storing DSC identifier information in memory, etc.) to register the DSC144 with the DPC 146. In an embodiment, as part of these registrationoperations, the DPC 146 may overwrite/override an existing registrationwith a new registration, such as in response to receiving a duplicateDSC REGISTER REQUEST message (i.e. for an already registered DSCidentified by the same unique DSC identity).

In operation block 806 illustrated in FIG. 8A, the DPC 146 may determinethat the registration operations were successful. In operation 808, theDPC 146 may generate and send a DSC REGISTER ACCEPT message to the DSC144 to indicate the acceptance and registration of the DSC 144. Invarious embodiments, the DPC 146 may generate the DSC REGISTER ACCEPTmessage to include any or all of a message type information element(IE), a message ID IE, a DPC ID IE, a XEh signaling transport networklayer (TNL) address IE, and a tunneling information IE. The XEhsignaling TNL address IE may include an address value that is suitablefor use in establishing to transport layer session. The tunnelinginformation IE may include information that may used to encapsulate adifferent payload protocol, establish a secured communication through anuntrusted or unverified network, carry a payload over an incompatibledelivery-network, and/or to perform other similar tunneling operations.

To support XEh connectivity via/to the DPC 146, in operation block 810,the DSC 144 may use the address value included in the XEh signaling TNLaddress IE of the DSC REGISTER ACCEPT message establish a transportlayer session. In an embodiment, the DSC 144 may be configured toestablish the transport layer session in response to determining thatthe DSC REGISTER ACCEPT message includes an address value in the XEhsignaling TNL address information element. In an embodiment, the DSC 144may be configured to determine that the XEh connectivity via/to the DPC146 is not supported or not required in response to determining that theXEh signaling TNL address information element is not present, null,empty, or not valid.

With reference to FIG. 8B, in operation block 812, the DPC 146 maydetermine that the registration operations performed as part ofoperation 804 failed. The DPC 146 may determine that registration failedin response to detecting any of a variety of conditions/events,including the failure to authenticate or authorize the DSC, network orcomponent overload, DSC parameter mismatch, etc. In operation 814, theDPC 146 may generate and send a DSC REGISTER REJECT message to the DSC144 to inform the DSC 144 that the registration failed and/or that theDPC 146 cannot register the DSC 144. In various embodiments, the DPC 146may generate the DSC REGISTER REJECT message to include any or all of amessage type information element (IE), a message ID IE, a cause IE, acriticality diagnostics IE, and a backoff timer IE. The cause IE mayinclude information suitable for identifying a specific reason for thefailure (e.g., overloaded, etc.) or for indicating that the reason forthe failure is not known or is unspecified.

In operation block 816, the DSC 144 may perform various registrationfailure-response operations based on the information included in thereceived REGISTER REJECT message. For example, the DSC 144 may wait fora duration indicated in the backoff timer IE of the received REGISTERREJECT message before reattempting registration with that same DPC 146in response to determining that the value of the cause IE in thereceived REGISTER REJECT message is set to “overload.”

With reference to FIG. 8C, in operation block 852, the DSC 144 may starta register response timer in response to sending a DSC REGISTER REQUESTmessage to the DPC 146 (e.g., as part of operation 802). In operationblock 854, the DSC 144 may determine that the register response timerexpired before the DSC 144 received a DSC REGISTER RESPONSE message. Inoperation 856, the DSC 144 may resend the DSC REGISTER REQUEST messageto the DPC 146 in response to determining that the timer expired beforeit received a corresponding DSC REGISTER RESPONSE message. In operationblock 858, the DSC 144 may restart or reset the register response timer.In operation 860, the DPC may send a DSC REGISTER RESPONSE message tothe DSC 144. In operation block 862, the DSC 144 may stop the registerresponse timer in response to receiving the DSC REGISTER RESPONSEmessage.

FIGS. 9A and 9B illustrate a DSAAP advertising method 900 foradvertising resources that are available for bidding/buying so as toallow the DPC 146 to store, organize, and/or make those resourcesavailable for bidding/allocation via a financial brokerage platform. Inthe examples illustrated in FIGS. 9A and 9B, the DSAAP advertisingmethod 900 is performed by processing cores in a DPC 146 component and aDSC 144 component, each of which may include all or portions of a DSAAPmodule/component.

In operation block 902 illustrated in FIGS. 9A and 9B, the DSC 144 maydetermine that there are resources available for allocation within cellsserviced by that DSC 144. In operation block 904, the DSC 144 maygenerate and send a DSC RESOURCE REGISTER REQUEST message to the DPC146. In various embodiments, the DSC 144 may generate the DSC RESOURCEREGISTER REQUEST message to include any or all of a message typeinformation element (IE), a message ID IE, a DSC identity IE, a DSC typeIE, a PLMN-ID list IE, resource availability IE, resource availabilitystart time IE, a data bandwidth IE, a list of grids IE, a bid or buy IE,a minimum bid amount IE, resource availability end time IE, a time ofthe day IE, a time duration IE, megabits per second (MBPS) IE, and acell identity IE.

The DSC identity IE may include information that may be used by the DPC146 to determine the identity of DSC 144. For example, the DSC identityIE may include a DSC pool ID, DSC instance information, and a PLMN ID ofthe network that the DSC is managing or representing. The DSC pool IDmay be a unique identifier of a pool of available resources and/or maybe the same as or similar to MME pool IDs and MME IDs in 3GPP EPCarchitecture.

The message ID IE may include a message identifier for the specific DSCRESOURCE REGISTER REQUEST message sent from the DSC 144. The DSC 144 andDPC 146 may be configured to use the message ID IE as a sequence numberto identify and correlate DSC RESOURCE REGISTER REQUEST, DSC RESOURCEREGISTER ACCEPT and/or DSC RESOURCE REGISTER REJECT messages.

The resource availability IE may include information suitable for use bythe DPC 146 in determining the PLMN ID of the network that isadvertising resources for allocation and use by other networks. The DPC146 may be configured to receive, store, and/or maintain resourceavailability IEs for multiple DSCs and/or for multiple differentnetworks (i.e. different PLMN IDs). As such, each resource availabilityIE may include information suitable for identifying one or more of thenetworks that are advertising resources.

The time of the day IE may include information suitable for use by theDPC 146 in determining the time of the day that the DSC 144 transmittedthe DSC RESOURCE REGISTER REQUEST message. The time duration IE mayinclude information that is suitable for use in determining a timeperiod during which the resources are to be made available for biddingor buying.

The data bandwidth IE may include information suitable for use indetermining the available bandwidth (e.g., in MBPS) for the timeduration specified in the optional time duration IE. The DPC 146 maydetermine that the bandwidth specified in the MBPS IE is to be madeavailable until that bandwidth is consumed by the winning bidder orbuyer in response to determining that the time duration IE is notincluded in the received DSC RESOURCE REGISTER REQUEST message (or inresponse to determining that the time duration IE does not include avalid value).

The list of grids IE may include information suitable for use indetermining grid identifiers for the locations of the network bandwidththat is to be made available for bidding or buying. The cell identity IEmay include information suitable for use in determining the individualcells within each grid (identified by grid ID and cell ID) that haveavailable resources offered for bidding or buying as part of the offerin the DSC RESOURCE REGISTER REQUEST message. The minimum bid amount IEmay include a monetary amount in a denomination or currency, such as inUnited States Dollars (USD).

In operation block 906 illustrated in FIG. 9A, the DPC 146 may acceptthe DSC's 144 resources for bidding. In operation 908, the DPC 146 maygenerate and send a DSC RESOURCE REGISTER RESPONSE or DSC RESOURCEREGISTER ACCEPT message to the DSC 144 to acknowledge that the resourceswere accepted. In various embodiments, the DPC 146 may generate the DSCRESOURCE REGISTER message to include any or all of a message typeinformation element (IE), a bid ID IE, and a message ID IE. The messageID IE may include the same message identifier value that is included inthe received DSC RESOURCE REGISTER REQUEST message. The DPC 146 and/orDSC may be configured to use the value of the message ID IE to identifyand correlate the DSC RESOURCE REGISTER REQUEST and DSC RESOURCEREGISTER ACCEPT messages. In operation block 910, the DPC 146 may store,organize, and/or make the network resources available for bidding orbuying via the financial brokerage platform.

In operation 912 illustrated in FIG. 9B, the DPC 146 may reject the DSCRESOURCE REGISTER REQUEST message and/or reject for bidding theresources identified in the received DSC RESOURCE REGISTER REQUESTmessage. The DPC 146 may reject the message/resources for a variety ofreasons and/or in response to detecting any of a variety of events orconditions. For example, the DPC 146 may reject the resources inresponse to determining that the DPC 146 is not accepting resources fromany operator, is not accepting resources for the specific operatoridentified in the received message, is not accepting the resourcesidentified in the message, that the DPC is overloaded, that there isinsufficient memory to store and service the resources available forbidding, etc. The DPC 146 may also reject the resource available messagein response to determining that an administrator of the DPC 146 hasdisabled further bidding from the specific PLMN ID included in the DSCRESOURCE REGISTER REQUEST message, from all the networks (e.g., all thePLMN IDs), etc.

In operation 914 illustrated in FIG. 9B, the DPC 146 may generate andsend a DSC RESOURCE REGISTER REJECT message to the DSC 144. In variousembodiments, the DPC 146 may generate the DSC RESOURCE REGISTER REJECTmessage to include any or all of a message type information element(IE), a message ID IE, a cause IE, and a criticality diagnostics IE. TheDPC 146 may also generate the DSC RESOURCE REGISTER REJECT message toinclude a message ID IE that includes a value that is the same as themessage identifier included in the DSC RESOURCE REGISTER REQUEST messagereceived from DSC 144. The DPC 146 and/or DSC 144 may be configured touse the value of the message ID IE to identify and correlate the DSCRESOURCE REGISTER REQUEST and DSC RESOURCE REGISTER REJECT messages.

In operation block 916, the DSC 144 may perform various resourceregistration failure response operations based on information includedin the received DSC RESOURCE REGISTER REJECT message. For example, theDSC 144 may use the information included in the DSC RESOURCE REGISTERREJECT message to determine whether to reattempt resource registrationwith the DPC 146, attempt to register the resources with another DPC,reattempt the registration with different resources, or perform any ofthe other DSC operations discussed in this application.

FIGS. 10A and 10B illustrate a DSAAP method 1000 for communicating alist of available resources in accordance with an embodiment. DSAAPmethod 1000 may be performed to inform lessee networks of the resourcebids or resources that are available for bidding/buying. In the examplesillustrated in FIGS. 10A and 10B, the DSAAP method 1000 is performed byprocessing cores in a DPC 146 component and a DSC 144 component, each ofwhich may include all or portions of a DSAAP module/component. In anembodiment, a lessee DSC 144 may be configured to perform DSAAP method1000 to retrieve/receive a list of available resources prior to that DSC144 bidding on, or requesting to lease or purchase, resources from theDPC 146.

In operation 1002 illustrated in FIGS. 10A and 10B, a lessee DSC 144 maygenerate and send an AVAILABLE BIDS REQUEST message to the DPC 146 torequest information on the resource bids that are available forallocation from lessor network(s) for bidding or buying. In variousembodiments, the lessee DSC 144 may generate the AVAILABLE BIDS REQUESTmessage to include any or all of a sequence number information element(IE), a message type IE, a PLMN list IE that includes one or more PLMNID IEs, a grid ID list IE that includes one or more Grid ID IEs.

In an embodiment, the lessee DSC 144 may be configured to requestspecific resources from a specific network by generating the AVAILABLEBIDS REQUEST message to include the PLMN ID of the desired network,which may be included in the PLMN ID IE of the PLMN list IE in theAVAILABLE BIDS REQUEST message.

In an embodiment, the lessee DSC 144 may be configured to requestresources from any available network by not populating the PLMN list IEin the generated AVAILABLE BIDS REQUEST message and/or by generating theAVAILABLE BIDS REQUEST message to not include a PLMN list IE and/or PLMNID value.

In an embodiment, the lessee DSC 144 may be configured to requestresources from a specific grid within a lessor network by generating theAVAILABLE BIDS REQUEST message to include the grid IDs of the desiredgrids, which may be included in the grid ID IE of the grid ID list IE inthe AVAILABLE BIDS REQUEST message.

In an embodiment, the lessee DSC 144 may be configured to requestresources from any or all grids within a specified PLMN ID in PLMN ID IEgrid by not populating the grid ID list IE in the generated AVAILABLEBIDS REQUEST message and/or by generating the AVAILABLE BIDS REQUESTmessage to not include a grid ID.

In operation block 1004 illustrated in FIGS. 10A and 10B, the DPC 146may determine whether the PLMN ID(s) and grid ID(s) included in thereceived AVAILABLE BIDS REQUEST message are valid. If the PLMN ID(s) andgrid ID(s) are incorrect, in operation block 1005, the DPC 146 maydetermine a reason code for the error/incorrect values. In operationblock 1006, the DPC 146 may determine whether there are resources/bidsavailable for each grid identified in the received AVAILABLE BIDSREQUEST message or for all the available grids (e.g., when the grid IDlist IE in the received AVAILABLE BIDS REQUEST message not include validvalues).

In operation 1008 illustrated in FIG. 10A, the DPC 146 may generate andsend an AVAILABLE BIDS RESPONSE message to the DSC 144. The DPC 146 maybe configured to generate the AVAILABLE BIDS RESPONSE message to includeany or all of a message type information element (IE), a message ID IE,a DSC identity IE, a PLMN-ID grid cell bid info list IE, a sequencenumber IE, a PLMN list IE that includes one or more PLMN ID IEs, and agrid list IE. In an embodiment, the PLMN list IE and grid list IE may beincluded in the PLMN-ID grid cell bid info list IE. In an embodiment,the grid list IE may include one or more cell ID list IEs that includeone or more cell ID IEs.

In various embodiments, the DPC 146 may generate the AVAILABLE BIDSRESPONSE message to also include any or all of an absoluteradio-frequency channel number (ARFCN) IE, a channel bandwidth IE, amegabit or megabyte IE for identifying total available bandwidth, a MBPSIE for identifying the peak data rate for the resource, a resourceavailable time IE, a resource expiration time IE, a bid/buy IE, abid/buy expiry time IE, a minimum bid amount IE, and a buy price IE. TheDPC 146 may generate the AVAILABLE BIDS RESPONSE message to include suchinformation for each PMLN, each resource, each grid, and/or each cellidentified in the message.

In an embodiment, the DPC 146 may be configured to generate theAVAILABLE BIDS RESPONSE message to include the list of PLMN ID, lists ofgrid ID(s) within each PLMN, and the available resources/bids withineach grid in response to determining that there are bids for resourcesavailable for auction.

In an embodiment, the DPC 146 may be configured to generate theAVAILABLE BIDS RESPONSE message to include the message type and sequencenumber IEs (or valid values for these IEs) in response to determiningthat there no resources/bids for resources available for auction by thatDPC 146 for the relevant networks/PLMN IDs. In an embodiment, the DPC146 may be configured to generate the AVAILABLE BIDS RESPONSE message toinclude a sequence number IE having the same value as in the sequencenumber IE included in the received AVAILABLE BIDS REQUEST message. In anembodiment, the DSC 144 may be configured to use the sequence number IEsin these request and response messages to correlate the messages.

In an embodiment, the DPC 146 may be configured to generate theAVAILABLE BIDS RESPONSE message to include a PLMN list IE that includesa PLMN ID and grid ID list IE. The grid ID list IE may include a list ofcells available for auction within the grid. The cell ID list IE mayinclude a cell ID, and for each cell, the ARFCN, channel bandwidth,total available bandwidth, peak data rate allowed, the time of day(e.g., in UTC) when the resources are available and when theyexpire/end, whether it's a bid or buy type auction, minimum bid amountor buy price, bid expiry time (e.g., in UTC), and other similarinformation.

In operation block 1010, the DSC 144 may use the information included inthe AVAILABLE BIDS RESPONSE message to identify the resources that areavailable for bidding, determine whether the DSC 144 will submit a bidfor the available resources, determine the resources for which the DSC144 will submit bids, and/or perform other similar operations.

With reference to FIG. 10B, in operation 1012, the DPC 146 may rejectthe AVAILABLE BIDS REQUEST message received from lessee DSC 144 bygenerating and sending a AVAILABLE BIDS REJECT message to the DSC 144.The DPC 146 may be configured to reject the AVAILABLE BIDS REQUESTmessage in response to determining (e.g., as part of operation 1004 or1006) that one or more of the PLMN IDs supplied in the request messageis not from any of the known networks, that one or more of the Grid IDssupplied in the request message is not valid with respect to thesupplied PLMN ID, and/or that there are no resources/bids available inthe relevant grids.

In an embodiment, the DPC 146 may be configured to generate theAVAILABLE BIDS REJECT message to include a message type informationelement (IE), a message ID IE, a cause IE, a criticality diagnostics IE,and a sequence number IE. The cause IE may include a reason code (e.g.,Invalid PLMN ID, Invalid Grid ID, etc.) for the rejection of theavailable bids request, which may be determined in operation block 1005.The sequence number IE may include the same sequence number value thatwas included in the AVAILABLE BIDS REQUEST message received from lesseeDSC 144. As such, the DPC 146 and/or DSC 144 may be configured to usesequence number IEs in the request and response messages to correlatethose messages.

In operation block 1014, the DSC 144 may use the information included inthe received AVAILABLE BIDS REJECT message to perform variousfailure-response operations. For example, the DSC 144 may determinewhether to send another AVAILABLE BIDS REQUEST message to the DPC 146,determine whether to send another AVAILABLE BIDS REQUEST message to adifferent DPC, etc.

FIGS. 11A and 11B illustrate a DSAAP bidding method 1100 of bidding forDSC resources, which allows different lessee networks to bid forresources that are available from lessor networks. In the examplesillustrated in FIGS. 11A and 11B, the DSAAP method 1100 is performed byprocessing cores in a DPC 146 component and a DSC 144 component, each ofwhich may include all or portions of a DSAAP module/component.

In an embodiment, the DSC 144 and/or DPC 146 may be configured toperform DSAAP method 1100 after the DSC 144 retrieves the list ofresources that are available for bidding (e.g., after performing DSAAPmethod 1000). In various embodiments, the DSC 144 and/or DPC 146 may beconfigured to perform DSAAP method 1100 continuously or repeatedly untilthe expiration of a bidding time. In an embodiment, the DPC 146 may beconfigured to select a winning bid (i.e., bid highest bid value) at theexpiry of a bidding time.

In operation 1102 of method 1100 illustrated in FIGS. 11A and 11B, thelessee DSC 144 may generate and send a DSC BID REQUEST message to theDPC 146 to bid for one or more of the resource that are determined to beavailable from a lessor network, (i.e., one or more of resourcesincluded the list of resources obtained via the performance of method1000). The lessee DSC 144 may be configured to generate the DSC BIDREQUEST message to include any or all of a message type informationelement (IE), a message ID IE, a DSC identity IE, a DSC type IE, bid IDIE, a PLMN ID IE, and a bid amount IE. The bid ID IE may includeinformation suitable for identifying a specific resource for which thelessee DSC 144 places a bid. The PLMN ID IE may include informationsuitable for use in identifying the PLMN ID of the network associatedwith the resources identified in the bid ID IE. The bid amount IE mayinclude a monetary amount in a currency (e.g., USD), or the bid value.

In an embodiment, the lessee DSC 144 may be configured to generate theDSC BID REQUEST message to include a bid amount IE value that is greaterthan a minimum bid amount specified in a bid listing for the specificresource/bid ID. In an embodiment, the lessee DSC 144 may be configuredto obtain the minimum bid amount and/or bid listing from the receivedAVAILABLE BIDS RESPONSE message (e.g., the message sent as part ofoperation 1008 illustrated in FIG. 10A).

In operation block 1104 illustrated in FIG. 11A, the DPC 146 may use theinformation included in the received DSC BID REQUEST message todetermine whether the bid (resource bid) is valid and is to be accepted,such as by determining whether the bid complies with the policies andrules of the DSA system and the requirements of the lessor network. Inoperation 1106, the DPC 146 may generate and send DSC BID ACCEPT messageto the DSC in response to determining that the bid is valid and/or is tobe accepted. The DPC 146 may be configured to generate the DSC BIDACCEPT message to include any or all of a message type informationelement (IE), a message ID IE, a bid ID IE, and other informationsuitable for informing the DSC 144 that the bid has been determined tobe valid and/or has been accepted.

It should be noted that, in the example discussed above, the DSC BIDACCEPT message informs the DSC 144 that the bid is valid/accepted, notthat lessee DSC 144 has won the bid. The winning lessee DSC may beinformed via DSC BID WON message when the DPC 146 determines that thebid time has expired and that lessee DSC is the highest bidder at thetime of bid expiry. Similarly, the DPC 146 may inform lessee DSC(s) whoparticipated in the bidding process but submitted losing bids that theydid not submit a winning bid via a DSC BID LOST message. The DSC BID WONmessage and DSC BID LOST message are discussed in more detail furtherbelow.

With reference to FIG. 11B, in operation block 1108, the DPC 146 may usethe information included in the received DSC BID REQUEST message todetermine that the bid is not valid and is not to be accepted. Forexample, the DPC 146 may use the received information to determine thatthe bid does not comply with the policies/rules of the DSA system and/ordoes not comply with the requirements of the lessor network (e.g., doesnot meet the minimum asking price, etc.). As further examples, the DPC146 may be configured to determine that the bid is not valid or is notto be accepted in response to determining that the bid amount specificin bid amount IE in the BID REQUEST message is not higher than theminimum bid, that the bid amount is not the highest among currentlyoffered bids, that the bid id included in the bid ID IE is invalid, orthat the bid/resource is no longer available for bidding (e.g., due toexpiry, end of auction, bid withdrawn or invalid bid id).

In operation 1110, the DPC 146 may generate and send a DSC BID REJECTmessage to the DSC 144. The DPC 146 may be configured to generate theDSC BID REJECT message to include any or all of a message typeinformation element (IE), a message ID IE, a bid ID IE, a cause IE, anda criticality diagnostics IE. The bid ID IE in the DSC BID REJECTmessage may include the same value as the bid identifier included in thereceived DSC BID REQUEST message. The cause IE may include a reason codeidentifying a reason for the rejection of the bid (e.g., minimum bid notmet, outbid, bid not found, etc.). In operation block 1112, the DSC 144may use information included in the received DSC BID REJECT message toperform various bid request failure-response operations, such asoperations to determine whether to rebid for the resources, to generatea new DSC BID REQUEST message that includes a valid bid ID, etc.

FIGS. 12A through 12D illustrate a DSAAP notification method 1200 ofinforming participating networks of the results of the biddingoperations. That is, DSAAP notification method 1200 may be performed toinform DSCs 144 of a result of an auction (e.g., that they submitted awinning bid, that they have been outbid, that they submitted a losingbid, that the auction was cancelled, etc.). In the examples illustratedin FIGS. 12A-12D, the DSAAP notification method 1200 is performed byprocessing cores in a DPC 146 component and a DSC 144 component, each ofwhich may include all or portions of a DSAAP module/component.

DSAAP notification method 1200 may be performed after the DPC 146notifies the DSC 144 that the bid has been accepted (e.g., afteroperation 1106 illustrated in FIG. 11). The DSAAP notification method1200 also may be performed after the expiry of a bidding time and/or inresponse to the DPC 146 detecting an event or condition (e.g., new bidreceived, outbid, etc.).

In operation block 1202 illustrated in FIG. 12A, the DPC 146 maydetermine that the bid amount specific in bid amount IE in the last,latest, or most current BID REQUEST message accepted from the DSC 144 isnot the highest among the current bids. In operation 1204, the DPC 146may generate and send a DSC BID OUTBID message to the DSC 144 to informthe lessee DSC 144 that its earlier bid was outbid by a higher bid fromanother lessee DSC and/or that their earlier bid is no longer valid. Invarious embodiments, the DPC 146 may generate the DSC BID OUTBID messageto include any or all of a message type information element (IE), amessage ID IE, a cause IE, a bid info IE, a criticality diagnostics IE,a DSC ID IE and a BID ID IE.

The DSC ID IE may include information that is suitable for use inidentifying the specific lessee DSC 144. The BID ID IE may include a bidID suitable for use in identifying the submitted bid that has beenoutbid. In operation block 1206, the lessee DSC 144 may perform variousbid-outbid failure-response operations, such as by determining whetherto submit a higher bid for the resources to that DPC 146, to submit abid to a different DPC 146, to drop existing calls to free bandwidth,etc.

With reference to FIG. 12B, in operation block 1210, the DPC 146 maydetermine that the bidding time has expired and that the bid amountspecific in bid amount IE in the last, latest, or most current BIDREQUEST message accepted from the DSC 144 is the highest among thecurrent bids. In operation 1212, the DPC 146 may generate and send a DSCBID WON message to the DSC 144 to inform the lessee DSC 144 that theirearlier bid is the winning bid. In various embodiments, the DPC 146 maygenerate the DSC BID WON message to include any or all of a message typeinformation element (IE), a message ID IE, a bid ID IE, a bid info IE, aDSC ID IE, and original bid details such as bandwidth, MBPS, durationand the winning bid amount, etc. The DSC ID IE may include informationthat is suitable for use in identifying the specific lessee DSC 144. Thebid ID IE may include a bid identifier suitable for identifying the bidthat won the resource auction/bidding operations.

In operation block 1214, the winning lessee DSC 144 may wait to receiveDSC RESOURCES ALLOCATED message from the DPC 146 before scheduling itsnetwork equipment and device (e.g., wireless devices) to start using theresources and/or for the resources to be made available for use (i.e.scheduling for the time of day when the resources will be ready for useby the winning lessee network). In operation block 1216, the DPC 146 mayclose the auction, such as by rejecting further bids from other networksfor the resources won by the bid submitted by lessee DSC 144.

With reference to FIG. 12C, in operation block 1220, the DPC 146 maydetermine that the bidding time has expired and that the bid amountspecific in bid amount IE in the last, latest, or most current BIDREQUEST message accepted from the DSC 144 is not the highest among thecurrent bids. In operation 1222, the DPC 146 may generate and send a DSCBID LOST message to the DSC 144 to inform the lessee DSC 144 that itsearlier bid has not won the bid and the auction/bid is closed due toanother lessee DSC winning the auction. In various embodiments, the DPC146 may generate the DSC BID LOST message to include any or all of amessage type information element (IE), a message ID IE, a bid ID IE, anda DSC ID IE. The DSC ID IE may include information that is suitable foruse in identifying the specific lessee DSC 144 that submitted the losingbid and/or to which the DSC BID LOST message is sent. The bid ID IE mayinclude a bid identifier suitable for use in identifying the submittedbid.

In operation block 1224, the lessee DSC 144 may perform various failureresponse operations, such as determining whether to submit a bid to forother available resources, whether to drop existing calls to free upresources, etc. In operation block 1226, the DPC 146 may close theauction and/or allow the losing lessee DSCs to bid for other availableresources.

With reference to FIG. 12D, in operation block 1230, the DPC 146 maydetermine that the auction for a network resource that the DSC 144previously submitted a bid has been cancelled. For example, the DPC 146may determine that the auction has been withdrawn by lessor networkoperator or that the auction has been cancelled by DPC operator foradministrative reasons. In operation 1232, the DPC 146 may generate andsend a DSC BID CANCELLED message to the DSC 144 to inform the lessee DSC144 that the auction has been cancelled. In various embodiments, the DPC146 may generate the DSC BID CANCELLED message to include any or all ofa message type information element (IE), a message ID IE, a bid ID IE, aDSC ID IE, and a cause IE. The DSC ID IE may include information that issuitable for use in identifying the specific lessee DSC 144. The bid IDIE may include a bid identifier suitable for use in identifying theresource/bid for which the auction has been cancelled. The cause IE mayinclude a reason code for the bid's cancellation (e.g., auctionwithdrawn, auction cancelled, etc.). In operation block 1234, the lesseeDSC 144 may perform various failure-response operations, such as bydetermining whether to submit a bid to a different DPC 146, to dropcalls, etc.

FIGS. 13A and 13B illustrate a DSAAP purchase method 1300 of allowing alessee network to make an immediate (or near immediate) purchase and/orclaim of use for a resource that is made available for allocation by alessor network. In the examples illustrated in FIGS. 13A and 13B, theDSAAP purchasing method 1300 is performed by processing cores in a DPC146 component and a DSC 144 component, each of which may include all orportions of a DSAAP module/component. In an embodiment, the DSC 144 andDPC 146 may be configured to perform DSAAP method 1300 after the DSC 144retrieves/receives a list of resources that are available for purchase(e.g., after performing DSAAP method 1000 discussed above with referenceto FIG. 10).

In operation block 1302 illustrated in FIGS. 13A and 13B, the lessee DSC144 may identify and select a specific resource for immediate purchasefrom the list of resources (e.g., list of resources obtained fromperforming DSAAP method 1000 discussed above). In various theembodiments, the lessee DSC 144 may select a resource that is scheduledfor bidding, that is currently being auctioned, that is only madeavailable for immediate purchase, etc. In operation 1304, the DSC 144may generate and send DSC BUY REQUEST message to the DPC 146 to requestto buy the identified/selected resources from a lessor network.

In various embodiments, the DSC 144 may generate the DSC BUY REQUESTmessage to include any or all of a message type information element(IE), a message ID IE, a DSC identity IE, a DSC type IE, a bid ID IE, abuy amount IE, and a PLMN ID IE. The PLMN ID IE may include informationsuitable for use in identifying the PLMN ID of the network associatedwith the bid, which may identified via the bid ID IE. The buy amount IEmay include the amount (e.g., in USD) of the bid (i.e., bid value)submitted by the lessee DSC 144.

In an embodiment, the DSC 144 may be configured to generate the DSC BUYREQUEST message to include a buy amount value that is equal to an amountidentified via a buy amount IE in a listing for the bid ID included in areceived AVAILABLE BIDS RESPONSE message (which is discussed above withreference to FIG. 10).

In operation block 1306 illustrated in FIG. 13A, the DPC 146 may use theinformation included in the received DSC BUY REQUEST message to identifythe requested resource, the network associated with the requestresource, whether the requested resource is currently being auctioned,whether the requested resource has been made available for immediatepurchase, a minimum purchase amount requested for the immediate purchaseof that resource, and/or whether the buy amount included in the receivedDSC BUY REQUEST message is equal to (or greater than) the requestedpurchase amount. In the example illustrated in FIG. 13A, as part ofoperation block 1306, the DPC 146 determines that the buy amountincluded in the received DSC BUY REQUEST message is greater than orequal to the requested purchase amount.

In operation 1308, the DPC 146 may generate and send a DSC BUY ACCEPTmessage to the DSC 144 to inform the lessee DSC 144 that it hassuccessfully purchased/leased the resource for use. In variousembodiments, the DPC 146 may generate the DSC BUY ACCEPT message toinclude any or all of a message type information element (IE), a messageID IE, and a bid ID IE. In operation block 1310, the DPC 146 mayterminate, stop, or close an active auction for that resource and/orperform similar operations so that the resource is no longer availablefor bidding or buying by other lessee DSCs.

With reference to FIG. 13B, in operation block 1312, the DPC 146 may usethe information included in the received DSC BUY REQUEST message (e.g.,as part of operation 1304) to determine that the bid (buy request) is tobe rejected. For example, the DPC 146 may determine that the buy amountspecific in buy amount IE in the received DSC BUY REQUEST message isless than the requested purchase amount. As another example, the DPC 146may determine that the bid ID value included in the bid ID IE isinvalid, or that the resource/bid is no longer available for bidding(due to expiry, end of auction, bid withdrawn, invalid bid ID, etc.).

In operation 1314, the DPC 146 may generate and send a DSC BUY REJECTmessage to the DSC 144. In various embodiments, the DPC 146 may generatethe DSC BUY REJECT message to include any or all of a message typeinformation element (IE), a message ID IE, a bid ID IE and a cause IE.The value of the bid ID IE may be the same as the bid identifierincluded in the DSC BUY REQUEST message received as part of operation1304. The cause IE may include a reason code for the rejection of thebuy request (e.g., requested purchase price not met, bid not found,etc.). In operation block 1316, the DSC 1316 may perform variousfailure-response operations, such as determining whether to submit a newpurchase request with a higher bid amount. In operation block 1318, theDPC 146 perform various operations so to make that resource availablefor bidding or buying by other lessee DSCs.

FIGS. 14A and 14B illustrate a DSAAP resource allocation method 1400 ofallocating resources in a lessor network for access and use bycomponents in a lessee network. In the examples illustrated in FIGS. 14Aand 14B, the DSAAP resource allocation method 1400 is performed byprocessing cores in a DPC 146 component, a lessee DSC 144 a component,and a lessor DSC 144 b component, each of which may include all orportions of a DSAAP module/component.

In operation block 1402 illustrated in FIGS. 14A and 14B, the DPC 146may determine that the lessee DSC 144 a has successfully purchased orwon an auction for a resource in a lessor network represented by thelessor DSC 144 b. In operation 1404 illustrated in FIG. 14A, the DPC 146may generate and send a DSC BID SUCCESS message to the lessor DSC 144 bto inform the lessor network that one or more of its allocatedresources/bids has been won by the lessee DSC 144 a.

In various embodiments, the DPC 146 may generate the DSC BID SUCCESSmessage to include any or all of a message type information element(IE), a message ID IE, a cause IE, and a criticality diagnostics IE. Ina further embodiment, the DPC 146 may be configured to generate the DSCBID SUCCESS message to also include any or all of a bid ID IE, a DSC IDIE, and a bid value IE. These additional information elements may beused to communicate information regarding the winning bid. For example,the bid ID IE may include a bid ID that corresponds to the bid thatsuccessfully participated in and won the auction for the resources. TheDSC ID IE may include the DSC ID of the auction winner (i.e., the lesseeDSC 144 a). The bid value IE may include the winning bid amount and/orthe purchase price of the resources.

In operation 1404, the lessor DSC 144 b may generate and send DSCRESOURCES ALLOCATED message to the DPC 146 to allocate/commit theresources for access and use by components in the lessee network. Thelessor DSC 144 b may be configured to generate DSC RESOURCES ALLOCATEDmessage to include any or all of a message type information element(IE), a message ID IE, a bid iD, a PLMN-ID Grid ID Cell ID list IE, aPLMN ID IE, a grid ID IE, list of cell IDs IE, and variousauction/resource details (e.g., bandwidth, MBPS, duration, etc.). In anembodiment, the PLMN ID IE, a grid ID IE, and list of cell IDs IE may beincluded in the PLMN-ID Grid ID Cell ID list IE. The PLMN ID IE mayinclude the PLMN ID of the lessor network allocating the resources,which may be the same PLMN ID/network identified in the winning bid. Thegrid ID IE and list of cell IDs IE may include information suitable foridentifying the grid/cells associated with the resources. These valuesmay be the same as the grid/cell values included in the winning bid.

In operation 1406, the DPC 146 may forward the received DSC RESOURCESALLOCATED message to the winning lessee DSC 144 a to enable the lesseeDSC 144 a to start using the allocated resources of lessor networkresources. In operation block 1408, the lessee DSC 144 a may scheduleits network equipment to start using lessor network resources from thetime of day specified as part of the bid and/or included in the receivedDSC RESOURCES ALLOCATED message.

With reference to FIG. 14B, in operation block 1410, the lessor DSC 144b may determine that the resources submitted for auction should bewithdrawn and/or to forego allocating the submitted resources to awinner of the auction. The lessor DSC 144 b may determine to withdrawthe resources after the DPC 146 determines that lessee network purchasedor won an auction for those resources and/or for any of a variety ofreasons (e.g., unforeseen or administrative reasons, etc.).

In operation 1412, the lessor DSC 144 b may generate and send a DSCRESOURCES WITHDRAWN message to the DPC 146 to withdraw the resources.The lessor DSC 144 b may generate the DSC RESOURCES WITHDRAWN message toinclude any or all of a message type information element (IE), a messageID IE, a bid ID IE, a cause IE, and a PLMN-ID Grid ID Cell ID list IE.The bid ID IE may include information that is suitable for use inidentifying the bid. The cause IE may include a reason code thatdescribes the reason for withdrawal of resource allocations (e.g.,resources not available, resources withdrawn, administrative, etc.).

In operation 1414, the DPC 146 may forward the received DSC RESOURCESWITHDRAWN message to the lessee DSC 144 a, which may have submitted awinning bid for the withdrawn resources. In operation block 1416, thelessee DSC 144 a may perform various failure-response operations, suchas determining whether to participate in another auction, whether to bidon a different resource, determining whether to drop calls to free upresources, etc.

FIGS. 15A and 15B illustrate an embodiment DSAAP backoff method 1500 ofselectively handing over a wireless device from a lessor network back tothe lessee's network to which the wireless device subscribes (i.e. itshome PLMN). In the examples illustrated in FIGS. 15A and 15B, the DSAAPbackoff method 1500 is performed by processing cores in a DPC 146component, a lessee DSC 144 a component, and a lessor DSC 144 bcomponent, each of which may include all or portions of a DSAAPmodule/component.

In operation block 1502 illustrated in FIGS. 15A and 15B, the lessor DSC144 b may determine that its network resources from the cells that arepart of a prior auction are in congestion. That is, the lessor DSC 144 bmay determine that it requires access or use of its allocated resources.In operation 1504, the lessor DSC 144 b may generate and send a DSCBACKOFF COMMAND message to the DPC 146 to selectively handover wirelessdevice(s) that are using the allocated resources of the lessor networkback to the lessee network (i.e. its home PLMN).

The lessor DSC 144 b may be configured to generate the DSC BACKOFFCOMMAND message to include any or all of a message type informationelement (IE), a message ID IE, a bid ID IE, a UE identity IE, ameasurement report IE, handoff cell information IE, a cause IE, and aDSC backoff response timer IE.

The UE identity IE may include information suitable for use indetermining identity related information for the wireless device (orUE), such as the international mobile subscriber identity (IMSI) of thewireless device or its network.

The measurement report IE may include the latest, last, or most recentmeasurement report E-UTRAN RRC message received by the lessor networkfor the identified wireless device (i.e., the wireless devices that arerequested to backoff to lessee network).

The bid ID IE may include a bid ID value corresponding to the bid thatsuccessfully participated in and completed/won the auction. The bid IDmay be used to identify the auction/contract associated with the backoffoperations (i.e., the auction/contract for which the resources wereallocated).

In an embodiment, the lessor DSC 144 b may be configured to determinewhether there are multiple bid IDs that correspond to a congested cell.In an embodiment, the lessor DSC 144 b may be configured to select thebid ID value from a plurality of bid IDs in response to determining thatthere are multiple bid IDs that correspond to a congested cell. Invarious embodiments, the lessor DSC 144 b may be configured to selectthe bid ID value based on an operator policy provisioned at the lessorDSC 144 b, based on a previous agreement, based on a policy/rulepreviously negotiated by lessor and lessee network operators, etc.

In operation 1506, the DPC 146 may forward the received DSC BACKOFFCOMMAND message to the lessee DSC 144 a. In operation block 1508, thelessee DSC 144 a may use the information in the UE identity IE of thereceived DSC BACKOFF COMMAND message identify wireless device(s) thatare to be subjected to the backoff operations (i.e., the wirelessdevices that are to be handed back).

In operation block 1510, the lessee DSC 144 a may use the informationincluded in the measurement report IE of the received DSC BACKOFFCOMMAND message to determine, identify, and/or select a target cell(within lessee network) to which the identified wireless device(s) areto be handed over (the lessor network may have previously enabledmeasurement reporting from the wireless devices, such as when theyattached, or were handed over, to the lessor network.)

In operation 1512, the lessee DSC 144 a may generate and send a DSCBACKOFF RESPONSE message to the DPC 146. The lessee DSC 144 a may beconfigured to generate the DSC BACKOFF RESPONSE message to include anyor all of a message type information element (IE), a message ID IE, abid ID IE, a UE identity IE, a handoff cell information IE, and a causeIE. In an embodiment, the lessee DSC 144 a may be configured to generatethe DSC BACKOFF RESPONSE message to include the cause IE (or a value forthe cause IE) in response to determining that a suitable target cell(within lessee network) could not be identified or selected for thehanded over. The value of the cause IE may identify a cause of thefailure, such as network overload, no appropriate target cell found, orunknown wireless device/UE. In an embodiment, the lessee DSC 144 a maybe configured to generate the DSC BACKOFF RESPONSE message to include avalue (e.g., target cell information) for the handoff cell informationIE in response to successfully identifying a target cell (within lesseenetwork) to which the wireless device may be handed over.

In operation 1514, the DPC 146 may identify the lessor DSC 144 a basedon the bid id IE included in the received DSC BACKOFF RESPONSE message,and forward the received DSC BACKOFF RESPONSE message to the lessor DSC144 b. In operation block 1516, the lessor DSC 144 b may determinewhether the received DSC BACKOFF RESPONSE message includes a handoffcell information IE (or a valid value for the handoff cell informationIE). In response to determining that the received DSC BACKOFF RESPONSEmessage includes a handoff cell information IE (or a valid value for thehandoff cell information IE), in operation block 1518, the lessor DSC144 b may use the target cell information included in the handoff cellinformation IE to encode a HANDOVER REQUIRED message. In operation block1520, the lessor DSC 144 b may and initiate 51 based handover procedureto handover the wireless device from lessor network to lessee network.

With reference to FIG. 15B, in operation block 1552, the lessor DSC 144b may determine that the DPC 146 has not responded to the DSC BACKOFFCOMMAND message (sent as part of operation 1504) within a time periodidentified in the DSC backoff response timer IE included in the DSCBACKOFF COMMAND message. Alternatively or additionally, in operationblock 1554, the lessor DSC 144 b may determine that there is significantor severe network congestion or administrative reasons that requirewithdraw of the allocation of all remaining network resources pertainingto the resources/bid id included or identified in the DSC BACKOFFCOMMAND message.

In operation 1556, the lessor DSC 144 b may generate and send a DSCRESOURCES WITHDRAWN message to the DPC 146. In operation 1558, the DPC146 may forward the received DSC RESOURCES WITHDRAWN message to thelessee DSC 144 a to withdraw the allocation of the remaining networkresources. In operation block 1560, the lessee DSC 144 a may performvarious resource withdrawn failure-response operations, such as droppingcalls, determining whether to bid for new resources, etc.

FIG. 16A illustrates an embodiment DSC initiated DSAAP de-registrationmethod 1600 for terminating operations. In the example illustrated inFIG. 16A, the DSC initiated DSAAP de-registration method 1600 isperformed by processing cores in a DPC 146 component and a DSC 144component, each of which may include all or portions of a DSAAPmodule/component.

In operation block 1602, the DSC 144 may determine that it needs toterminate DSA operations. In operation 1604, the DSC 144 may generateand send a DSC DE-REGISTER message to the DPC 146. The DSC 144 may beconfigured to generate the DSC DE-REGISTER message to include any or allof a message type information element (IE), a message ID IE, a backofftimer IE, and a cause IE that identifies a cause for the termination ofoperations. In operation block 1606, the DPC 146 may clear all therelated resources associated with the DSC 144 and/or perform othersimilar operations to de-register the DSC 144 in response to receivingthe DSC DE-REGISTER message.

FIG. 16B illustrates an embodiment DPC initiated DSAAP de-registrationmethod 1650 for terminating operations. In the example illustrated inFIG. 16B, the DPC initiated DSAAP de-registration method 1650 isperformed by processing cores in a DPC 146 component and a DSC 144component, each of which may include all or portions of a DSAAPmodule/component.

In operation block 1652, the DPC 146 may determine that it needs toterminate DSA operations with the DSC 144. In operation 1654, the DPC146 may generate and send a DSC DE-REGISTER message to the DSC 144. TheDPC 146 may be configured to generate the DSC DE-REGISTER message toinclude any or all of a message type information element (IE), a messageID IE, a backoff timer IE, and a cause IE that identifies a cause forthe termination of operations (e.g., overload, unspecified, etc.). Inoperation block 1656, the DPC 146 may clear all the related resourcesassociated with the DSC 144 and/or perform other similar operations tode-register the DSC 144.

In operation block 1658, the DSC 144 may perform various de-registrationfailure response operations based on the information included in thereceived DSC DE-REGISTER message. For example, the DSC 144 may beconfigured to not retry registration to the same DPC 146 for at leastthe duration indicated in the backoff timer IE included in the receivedDSC DE-REGISTER message when the value of the cause IE in the DSCDE-REGISTER message is set to “overload.”

FIG. 17A illustrates a DSC initiated DSAAP error indication method 1700for reporting errors in accordance with an embodiment. In the exampleillustrated in FIG. 17A, method 1700 is performed by processing cores ina DPC 146 component and a DSC 144 component, each of which may includeall or portions of a DSAAP module/component.

In operation block 1702, the DSC 144 may detect an error or errorcondition (e.g., a protocol error, etc.). In operation 1704, the DSC 144may generate and send an ERROR INDICATION message to the DPC 146. TheDSC 144 may be configured to generate the ERROR INDICATION message toinclude any or all of a message type information element (IE), a messageID IE, cause IE, and a criticality diagnostics IE. The cause IE mayinclude information suitable for use in identifying a cause or type ofthe error (e.g., transfer syntax error, abstract syntax error, logicalerror, etc.). The criticality diagnostics IE may include a procedurecode IE, a triggering message IE, and a procedure criticality IE. Inoperation block 1706, the DSC 144 and/or DPC 146 may perform variouserror-response operations based on the detected error or informationincluded in the received ERROR INDICATION message. The error detectionand response operations are discussed in detail further below.

FIG. 17B illustrates an embodiment DPC initiated DSAAP error indicationmethod 1750 for reporting errors in accordance with another embodiment.In the example illustrated in FIG. 17B, method 1750 is performed byprocessing cores in a DPC 146 component and a DSC 144 component, each ofwhich may include all or portions of a DSAAP module/component.

In operation block 1752, the DPC 146 may detect an error condition. Inoperation 1754, the DPC 146 may generate and send an ERROR INDICATIONmessage to the DSC 144. The DPC 146 may be configured to generate theERROR INDICATION message to include a cause information element (IE)that identifies a cause for the error. In operation block 1756, the DSC144 and/or DPC 146 may perform various error-response operations basedon the information included in the received ERROR INDICATION message.

As mentioned above, the DSC 144 and DPC 146 may be configured performvarious error-response or failure response operations in response todetecting an error or failure condition. As part of these operations,the DSC 144 and/or DPC 146 may identify the type or cause of theerror/failure condition, and tailor their responses based on theidentified type or cause. For example, the DSC 144 and/or DPC 146 may beconfigured to determine whether a detected error is a protocol error,and tailor their responses accordingly.

Protocol errors include transfer syntax errors, abstract syntax errors,and logical errors. A transfer syntax error may occur when the receivingfunctional DSAAP entity (e.g., DSC, DPC, etc.) is not able to decode thereceived physical message. For example, transfer syntax errors may bedetected while decoding ASN.1 information in a received message. In anembodiment, the DSC 144 and DPC 146 components may be configured toretransmit or re-request a DSAAP message in response to determining thata detected error is a transfer syntax error (e.g., as part of theerror-response operations).

An abstract syntax error may occur when the receiving functional DSAAPentity (e.g., DSC, DPC, etc.) receives information elements (IEs) or IEgroups that cannot be comprehended or understood (i.e., an unknown IEid). An abstract syntax error may also occur when the entity receives aninformation element (IE) for which a logical range (e.g., allowed numberof copies) is violated. The DSC 144 and DPC 146 components may beconfigured to detect or identify these types of abstract syntax errors(i.e., cannot comprehend abstract syntax error), and in response,perform error-response operations based on criticality informationincluded in the corresponding DSAAP message. Additional detailsregarding these operations and the criticality information are providedfurther below.

An abstract syntax error may also occur when the receiving functionalDSAAP entity does not receive IEs or IE groups, but according to thespecified presence of the object, the IEs or IE groups should have beenpresent in the received message. The DSC 144 and DPC 146 components maybe configured to detect or identify these particular types of abstractsyntax errors (i.e., missing IE or IE group), and in response, performerror-response operations based on criticality information and presenceinformation for the missing IE/IE group. Additional details regardingthese operations, criticality information, and presence information areprovided further below.

An abstract syntax error may also occur when the receiving entityreceives IEs or IE groups that are defined to be part of that message inwrong order or with too many occurrences of the same IE or IE group. Inaddition, an abstract syntax error may also occur when the receivingentity receives IEs or IE groups, but according to the conditionalpresence of the concerning object and the specified condition, the IEsor IE groups should not have been present in the received message. TheDSC 144 and DPC 146 components may be configured to detect or identifysuch abstract syntax errors (i.e., wrong order, too many occurrences,erroneously present, etc.), and in response, reject or terminate aprocedure or method associated with the error (e.g., the method thatcaused the error). The DSC 144 and DPC 146 components may reject orterminate the procedure/method as part of the error-response operations.

In the various embodiments, the DSC 144 and DPC 146 components may beconfigured to continue to decode, read, or process a DSAAP message afterdetecting, identifying, or determining that an abstract syntax erroroccurred for that message. For example, the DSC 144 and DPC 146components may skip a portion of the message that includes an error, andcontinue processing the other portions of the message. As part of thiscontinued processing, the DSC 144 and DPC 146 components may detect oridentify additional abstract syntax errors.

In an embodiment, the DSC 144 and DPC 146 components may be configuredto perform error-response operations for each detected abstract syntaxerror and/or based on the criticality information and presenceinformation for the IE/IE group associated with the abstract syntaxerror.

As mentioned above, each DSAAP message may include, or may be associatedwith, criticality information, presence information, range information,and assigned criticality information. In the various embodiments, areceiving functional DSAAP entity (e.g., DSC, DPC, etc.) may beconfigured to use any or all of such information (e.g., criticalityinformation, presence information, etc.) when detecting an error,identifying the type of the error, or the specific error-response thatare to be performed. That is, the entity may perform differentoperations depending on the values of the criticality information,presence information, range information, and/or assigned criticalityinformation.

In an embodiment, the receiving functional DSAAP entity (e.g., DSC, DPC,etc.) may be configured to use the presence information included in aDSAAP message when identifying the type of error and the specificerror-response operations that are to be performed for the identifiederror type. For example, the entity may use the presence information todetermine whether the presence of an information element (IE) isoptional, conditional, or mandatory (e.g., with respect to RNSapplication) for that message or communication. The entity may determinethat an abstract syntax error has occurred when a received message ismissing one or more information elements that are determined to bemandatory (or conditional when the condition is true).

In an embodiment, the receiving functional DSAAP entity (e.g., DSC, DPC,etc.) may be configured use the criticality information when identifyingthe specific error-response operations that are to be performed. Thatis, each DSAAP message may include criticality information for eachindividual information element (IE) or IE group included in thatmessage. The values of criticality information for each IE or IE groupmay include “Reject IE,” “Ignore IE and Notify Sender,” and “Ignore IE.”The receiving entity (e.g., DSC, DPC, etc.) may use this criticalityinformation to determine that an IE, an IE group, or an EP isincomprehensible, identify the condition as an abstract syntax error(i.e., a cannot comprehend abstract syntax error), and/or to identifythe error-response operations that are to be performed (e.g., reject,ignore, notify, etc.).

In an embodiment, the receiving entity (e.g., DSC, DPC, etc.) may beconfigured to reject a method/procedure and initiate a DSAAP errorindication method (discussed above with reference to FIGS. 17A-B) inresponse to determining that an information element (IE) included in amessage received during the performance of that method/procedure isincomprehensible, and that value of the criticality information for thatIE is set to “Reject IE.”

For example, when a message that initiates a method/procedure (e.g., aDSC REGISTER REQUEST message, etc.) is received, determined to includeone or more IEs/IE groups that are incomprehensible and marked as“Reject IE,” the receiving entity may the reject the method/procedure bynot executing any of the functional requests included in that message.The receiving entity may also report the rejection of one or more IEs/IEgroups using the message normally used to report unsuccessful outcome ofthe procedure. When the information in the received initiating messageis insufficient and cannot be used to determine a value for all IEs thatare required to be present in the message used to report theunsuccessful outcome of the procedure, the receiving entity mayterminate the procedure and initiate a DSAAP error indicationmethod/procedure.

As a further example, when a message initiating a method/procedure thatdoes not have a message to report unsuccessful outcome is received, andthat message includes one or more IEs/IE groups marked with “Reject IE”which the receiving entity does not comprehend, the receiving entity mayterminate the method/procedure and initiate a DSAAP error indicationmethod/procedure.

As yet another example, when a response message (e.g., a DSC REGISTERRESPONSE message, etc.) is received that includes one or more IEs markedwith “Reject IE” which the receiving entity does not comprehend, thereceiving entity may consider the method/procedure as beingunsuccessfully terminated, and initiate a local error handling method.

In an embodiment, the receiving entity (e.g., DSC, DPC, etc.) may beconfigured to ignore or skip a method/procedure and initiate an DSAAPerror indication method (discussed above with reference to FIGS. 17A-B)in response to determining that an information element (IE) included ina message received during the performance of that method/procedure isincomprehensible, and that value of the criticality information for thatIE is set to “Ignore IE and Notify Sender.”

As an example, when a message initiating a method/procedure is receivedcontaining one or more IEs/IE groups marked with “Ignore IE and NotifySender” which the receiving entity does not comprehend, the receivingentity may ignore the content of the incomprehensible IEs/IE groups,continue with the method/procedure as if the incomprehensible IEs/IEgroups were not received (except for the reporting) using thecomprehended IEs/IE groups, and report in the response message of themethod/procedure that one or more IEs/IE groups have been ignored. Whenthe information received in the initiating message is insufficient todetermine a value for all IEs that are required to be present in theresponse message, the receiving entity may terminate themethod/procedure and initiate a DSAAP error indication method/procedure.

As a further example, when a message initiating a method/procedure thatdoes not have a message to report the outcome of the method/procedure isreceived containing one or more IEs/IE groups marked with “Ignore IE andNotify Sender” which the receiving entity does not comprehend, thereceiving entity may ignore the content of the not comprehended IEs/IEgroups, continue with the method/procedure as if the not comprehendedIEs/IE groups were not received (except for the reporting) using theunderstood IEs/IE groups, and initiate a DSAAP error indicationmethod/procedure to report that one or more IEs/IE groups have beenignored.

As yet another example, when a response message is received containingone or more IEs/IE groups marked with “Ignore IE and Notify Sender”which the receiving entity does not comprehend, the receiving entity mayignore the content of the not comprehended IE/IE groups, continue withthe method/procedure as if the not comprehended IEs/IE groups were notreceived (except for the reporting) using the understood IEs/IE groupsand initiate a DSAAP error indication method/procedure.

In an embodiment, the receiving entity (e.g., DSC, DPC, etc.) may beconfigured to ignore or skip a method/procedure in response todetermining that an information element (IE) included in a messagereceived during the performance of that method/procedure isincomprehensible, and that value of the criticality information for thatIE is set to “Ignore IE.”

As an example, when a message initiating a method/procedure is receivedcontaining one or more IEs/IE groups marked with “Ignore IE” which thereceiving entity does not comprehend, the receiving entity may ignorethe content of the not comprehended IEs/IE groups and continue with themethod/procedure as if the not comprehended IEs/IE groups were notreceived using only the understood IEs/IE groups.

As a further example, when a response message is received that includesone or more IEs/IE groups marked with “Ignore IE” which the receivingentity does not comprehend, the receiving entity may ignore the contentof the not comprehended IEs/IE groups and continue with themethod/procedure as if the not comprehended IEs/IE groups were notreceived using the understood IEs/IE groups.

When reporting not comprehended IEs/IE groups marked with “Reject IE” or“Ignore IE and Notify Sender” using a response message defined for themethod/procedure, the Information Element Criticality Diagnostics IE maybe included in the Criticality Diagnostics IE for each reported IE/IEgroup.

In an embodiment, the receiving entity (e.g., DSC, DPC, etc.) may beconfigured to initiate a DSAAP error indication method (discussed abovewith reference to FIGS. 17A-B) in response to determining that it cannotdecode a type of message IE in a received message. In an embodiment, theentity may be configured to only consider the IEs specified in thespecification version used by the component when determining the correctorder for the IE included in a message.

In an embodiment, the receiving entity (e.g., DSC, DPC, etc.) may beconfigured to treat the missing IE/IE group according to the criticalityinformation for the missing IE/IE group in the received messagespecified in the version of the present document used by the receiver.

As an example, the receiving entity (e.g., DSC, DPC, etc.) may beconfigured to not execute any of the functional requests of a receivedinitiating message in response to determining that the received messageis missing one or more IEs/IE groups with specified criticality “RejectIE.” The receiving entity may reject the method/procedure and report themissing IEs/IE groups using the message normally used to reportunsuccessful outcome of the method/procedure. When it is determined thatthe information received in the initiating message was insufficient todetermine a value for all IEs that are required to be present in themessage used to report the unsuccessful outcome of the method/procedure,the receiving entity may terminate the method/procedure and initiate aDSAAP error indication method/procedure.

As a further example, when a received message initiating amethod/procedure that does not have a message to report unsuccessfuloutcome is missing one or more IEs/IE groups with specified criticality“Reject IE”, the receiving entity may terminate the method/procedure andinitiate a DSAAP error indication method/procedure.

As yet another example, when a received response message is missing oneor more IEs/IE groups with specified criticality “Reject IE, thereceiving entity may consider the method/procedure as unsuccessfullyterminated and initiate a local error handling method/procedure.

As another example, when a received message initiating amethod/procedure is missing one or more IEs/IE groups with specifiedcriticality “Ignore IE and Notify Sender”, the receiving entity mayignore that those IEs are missing and continue with the method/procedurebased on the other IEs/IE groups present in the message and report inthe response message of the method/procedure that one or more IEs/IEgroups were missing. When the information received in the initiatingmessage is insufficient to determine a value for all IEs that arerequired to be present in the response message, the receiving entity mayterminate the method/procedure and initiate a DSAAP error indicationmethod/procedure.

As another example, when a received message initiating amethod/procedure that does not have a message to report the outcome ofthe method/procedure is missing one or more IEs/IE groups with specifiedcriticality “Ignore IE and Notify Sender”, the receiving entity mayignore that those IEs are missing and continue with the method/procedurebased on the other IEs/IE groups present in the message and initiate aDSAAP error indication method/procedure to report that one or moreIEs/IE groups were missing.

As another example, when a received message a received response messageis missing one or more IEs/IE groups with specified criticality “IgnoreIE and Notify Sender”, the receiving entity may ignore that those IEsare missing and continue with the method/procedure based on the otherIEs/IE groups present in the message and initiate a DSAAP errorindication method/procedure to report that one or more IEs/IE groupswere missing.

As another example, when a received message initiating amethod/procedure is missing one or more IEs/IE groups with specifiedcriticality “Ignore IE”, the receiving entity may ignore that those IEsare missing and continue with the method/procedure based on the otherIEs/IE groups present in the message.

As another example, when a received response message is missing one ormore IEs/IE groups with specified criticality “Ignore IE”, the receivingentity may ignore that those IEs/IE groups are missing and continue withthe method/procedure based on the other IEs/IE groups present in themessage.

The receiving entity (e.g., DSC, DPC, etc.) may be configured to respondto messages that include IEs or IE groups that received in wrong order,include too many occurrences, or are erroneously present (i.e., areincluded and marked as “conditional” when the condition is not met) invarious ways. For example, the receiving entity (e.g., DSC, DPC, etc.)may be configured to not execute any of the functional requests of areceived initiating message in response to determining that the receivedmessage includes IEs or IE groups in wrong order, includes too manyoccurrences of an IE, or includes erroneously present IEs. The receivingentity may reject the method/procedure and report the cause value“Abstract Syntax Error (Falsely Constructed Message)” using the messagenormally used to report unsuccessful outcome of the method/procedure.When the information received in the initiating message is insufficientto determine a value for all IEs that are required to be present in themessage used to report the unsuccessful outcome of the method/procedure,the receiving entity may terminate the method/procedure and initiate aDSAAP error indication method/procedure.

As another example, when a message initiating a method/procedure thatdoes not have a message to report unsuccessful outcome is receivedcontaining IEs or IE groups in wrong order or with too many occurrencesor erroneously present, the receiving entity may terminate themethod/procedure, and initiate a DSAAP error indication method/procedureusing the cause value “Abstract Syntax Error (Falsely ConstructedMessage)”.

As another example, when a response message is received containing IEsor IE groups in wrong order or with too many occurrences or erroneouslypresent, the receiving entity may consider the method/procedure asunsuccessfully terminated and initiate local error handling.

As mentioned above, protocol errors include transfer syntax errors,abstract syntax errors, and logical errors. A logical error occurs whena message is comprehended correctly, but the information containedwithin the message is not valid (i.e. semantic error), or describes amethod/procedure which is not compatible with the state of the receivingentity.

In an embodiment, a receiving entity (e.g., DSC, DPC, etc.) may beconfigured to perform error response operations based on the class ofthe method/procedure and irrespective of the criticality information ofthe IE's/IE groups containing the erroneous values in response todetermining/detecting an logical error.

For example, when a logical error is detected in a request message of aclass 1 method/procedure, and the method/procedure has a message toreport this unsuccessful outcome, this message may be sent with anappropriate cause value (i.e., in the clause IE), such as “semanticerror” or “message not compatible with receiver state.” When a logicalerror is detected in a request message of a class 1 method/procedure,and the method/procedure does not have a message to report thisunsuccessful outcome, the method/procedure may be terminated and a DSAAPerror indication method/procedure may be initiated with an appropriatecause value. Where the logical error exists in a response message of aclass 1 procedure, the procedure may be considered as unsuccessfullyterminated and local error handling may be initiated.

When a logical error is detected in a message of a class 2 procedure,the procedure may be terminated and a DSAAP error indication proceduremay be initiated with an appropriate cause value.

In the various embodiments, the receiving entity (e.g., DSC, DPC, etc.)may be configured to perform a local error handling method/procedure (asopposed to a DSAAP error indication method/procedure) when a protocolerror is detected in the ERROR INDICATION message. In case a responsemessage or error indication message needs to be returned, but theinformation necessary to determine the receiver of that message ismissing, the procedure may be considered as unsuccessfully terminatedand local error handling may be initiated. When an error that terminatesa procedure occurs, the returned cause value may reflect the error thatcaused the termination of the procedure even if one or more abstractsyntax errors with criticality “ignore and notify” have earlier occurredwithin the same procedure.

FIG. 18A illustrates an embodiment HSS user profile management method1800 for updating the information stored in or managed by an MME 130.The HSS user profile management method 1800 may be performed byprocessing cores in a HSS 130 component and a MME 130 component, each ofwhich may include all or portions of a DSAAP module/component.

In operation block 1802, the HSS 132 may monitor HSS user profilerepository to determine whether the HSS information (e.g., HSS userprofile information) has been changed for a wireless device (or for awireless device user/subscriber). In the example illustrated in FIG.18A, the HSS 132 detects that the HSS information has changed in block1802. In operation block 1804, the HSS 132 may determine whether thedetected changes affect the HSS user profile stored in an MME 130associated with the wireless device. For example, the HSS 132 maydetermine whether the changed HSS information identifies a new QoS levelthat is to be provided to the wireless device, that the wireless deviceis allowed to use resources of a lessor network (e.g., via the lesseenetwork winning a bid), etc.

In operation 1806, the HSS 132 may generate and send a HSS INSERTSUBSCRIBER DATA communication message to the MME 130 in response todetermining that the detected changes affect the MME 130. The HSS 132may generate the HSS INSERT SUBSCRIBER DATA message to includeinformation suitable for informing the MME 130 of the changes to the HSSinformation, such as an IMSI value and the changed subscriptioninformation/data. In an embodiment, the HSS INSERT SUBSCRIBER DATAmessage may be a “changed data” communication message.

In operation block 1808, the MME 130 may receive the HSS INSERTSUBSCRIBER DATA message, and use the information included in thereceived message to add, remove, or modify stored user profileinformation of the MME 130. In operation block 1812, the MME processingcore may perform additional operations to initiate appropriate actionsin response to the changes, if necessary. For example, in operationblock 1812, the MME 130 may initiate a detach procedure in response todetermining the wireless device is not allowed to roam in the networkbased on the information included in the HSS INSERT SUBSCRIBER DATA. Forreceived PDN subscription contexts that have no related active PDNconnection in the MME 130, no further operations may be required inblock 1812. Otherwise, if the subscribed QoS Profile has been modifiedand the wireless device is in ECM CONNECTED state or in ECM-IDLE statewhen ISR is not activated, an HSS-initiated subscribed QoS modificationprocedure/method may be invoked or performed in block 1812. If thewireless device is in ECM IDLE state and the ISR is activated, then theMME 130 may invoke or perform the HSS-initiated subscribed QoSmodification procedure/method at the next ECM IDLE to ECM CONNECTEDtransition. If the wireless device is in ECM IDLE state and the ISR isnot activated (and if the subscription changes no longer allows the PDNconnection) the MME 130 may initiate a PDN disconnection procedure todelete the concerned PDN connection. If the wireless device is inECM-CONNECTED state and connected via a CSG or hybrid cell, the MME 130may check the received CSG subscription data to determine whether theCSG membership to that cell has changed or expired. If the MME 130detects that the CSG membership to that cell has changed or expired, theMME 130 may perform various operations to respond accordingly.

In operation 1812, the MME 130 may generate and send a HSS INSERTSUBSCRIBER DATA ACKNOWLEDGMENT message to the HSS 132. The MME 130 maygenerate the HSS INSERT SUBSCRIBER DATA ACKNOWLEDGMENT message toinclude the IMSI value and information suitable for informing the MME130 of the changes to the user profile information and/or the results ofthe additional operations. In operation block 1812, the HSS processingcore may receive the HSS INSERT SUBSCRIBER DATA ACKNOWLEDGMENT message,and use the information included in the received message to update itsinformation to match the MME 130.

FIG. 18B illustrates an embodiment method 1850 of purging information.Method 1850 may be performed by processing cores in a HSS 130 componentand a MME 130 component, each of which may include all or portions of aDSAAP module/component.

In operation block 1852, the MME 130 may determining whethersubscription data and mobility management context information of adetached wireless device have been deleted, and delete user profileinformation and subscription data corresponding to the detached wirelessdevice. The MME 130 may delete the subscription data and mobilitymanagement context information immediately after the implicit orexplicit detach, or keep the information for a preset period of time sothat the data may be reused at a later attach without accessing the HSS132.

In operation 1854, the MME 130 may generate and send a PURGE UEcommunication message to the HSS 132. In operation block 1856, the HSS132 may update its information and records to reflect that the wirelessdevice has detached. For example, the HSS 132 may set a “UE Purged forE-UTRAN” flag. In operation 1858, the HSS 132 may generate and send aPURGE UE ACKNOWLEDGMENT message to the MME 130.

FIG. 18C illustrates an embodiment method 1870 of requesting subscriberdata from a home subscriber server (HSS). Method 1870 may be performedby processing cores in a HSS 130 component and a DSC 1144 component,each of which may include all or portions of a DSAAP module/component.

In operation block 1854, the DSC 144 may being performing resourceallocation operation for a DSA lease (e.g., for a winning bid thatallows the lessee network to use the resources of a lessor network). Inoperation block 1874, the DSC 144 may obtain a network identifier orPLMN for the lease (e.g., identified in the winning bid) and initiate aninquiry to the lessee HSS 132. In operation 1876, the DSC 144 maygenerate and send a SUBSCRIBER DATA REQUEST message to the HSS 132component.

In operation block 1878, the HSS 132 may use the information included inthe received SUBSCRIBER DATA REQUEST message to identify and selectwireless device subscribers that are allowed to use the lessor resourcesunder the DSA lease along with their user profile information, such asQoS or service pack definition information. In addition, the HSS 132 maythe information included in the received SUBSCRIBER DATA REQUEST messageto update the user profile information, if necessary. In operation 1880,the HSS 132 may generate and send a SUBSCRIBER DATA RESPONSE message tothe DSC 144 component. In various embodiments, the HSS 132 may generatethe SUBSCRIBER DATA RESPONSE message to include information about awireless device's location, IP address, QoS profile, access restrictionsfor roaming, PDNs to which the wireless device is allowed to connect, anAPN or a PDN address that indicates one or more subscribed IP addresses,an identity of the MME to which a wireless device is currently attachedor registered, etc.

FIG. 19 illustrates an embodiment HSS method 1900 of updating userprofile information in a mobility management entity (MME). Method 1900may be performed in a processing core of a HSS component.

In block 1902, the processing core may receive user profile information,subscriber data, wireless device information, and/or DSA informationfrom DSC. For example, the processing core may receive updatedinformation about a wireless device's location, IP address, QoS profile,access restrictions for roaming, PDNs to which the wireless device isallowed to connect, an APN or a PDN address that indicates one or moresubscribed IP addresses, an identity of the MME to which a wirelessdevice is currently attached or registered, etc. Also in block 1902, theprocessing core may determine whether any of the HSS information storedin a memory of the HSS component should be updated in view of theinformation received from the DSC component.

In block 1904, the processing core may determine whether HSS information(e.g., HSS user profile information) stored in a memory of the HSS haschanged for a wireless device (e.g., in response to the receivingupdated information from the DSC). In various embodiments, the HSSinformation may include user profile information, subscriptioninformation, wireless device location information, IP addressinformation, QoS profile information, access restrictions for roaming,PDNs to which the wireless device is allowed to connect, an APN or a PDNaddress that indicates one or more subscribed IP addresses, an identityof the MME to which a wireless device is currently attached orregistered, an international mobile subscriber identity (IMSI) value, anetwork access mode (NAM) value, an international mobile equipmentidentity (IMEI), a wireless device type identifier, data related toauthentication and ciphering, data related to roaming permissions,wireless device status information, data related to operator-determinedbarring, trace information, a privacy exception list, service typeinformation, charging information, and/or any information commonlystored by a HSS component and/or is a subscriber profile repository.

In block 1906, the processing core may determine whether the changes tothe HSS information affect information stored in a user profilerepository of the MME. In block 1908, the processing core may generate achanged data communication message that includes information identifyingthe changes to the HSS information stored in the memory of the HSS. Inblock 1910, the processing core may send the generated changed datacommunication message to the MME via the first communication link.

FIG. 20 illustrates an embodiment MME method 2000 for updating userprofile information and modifying the quality of service (QoS) for awireless device. Method 2000 may be performed in a processing core of aMME component. In block 2002, the processing core may receive a changeddata communication message from a HSS component. In block 2004, theprocessing core may use information included in the received changeddata communication message to modify user profile information stored ina user profile repository of MME. In block 2006, the processing core mayuse information included in the received changed data communicationmessage to determine whether a public data network (PDN) subscriptioncontext has a related active PDN connection in the MME. In block 2008,the processing core may use information included in the received changeddata communication message to determine whether a subscribed quality ofservice (QoS) profile has been modified.

In block 2010, the processing core may perform subscribed QoSmodification operations in response to determining the QoS profile hasbeen modified. Performing subscribed QoS modification procedures/methodsmay include performing various operations to increase or reduce the QoSprovided to the subscriber group or wireless device (e.g., degrade theQoS of a data connection to reduce congestion at an eNodeB) and/or toupdate QoS information that stored or managed by the MME or HSScomponents. In an embodiment, in block 2010, the processing core mayinitiate a QoS modification procedure/method in response to determiningthat the subscribed QoS profile has been modified, the wireless deviceis in one of the ECM CONNECTED or ECM-IDLE states, and/or that ISR hasnot been activated. In a further embodiment, in block 2010, theprocessing core may initiate (or cause the HSS component to initiate)the subscribed QoS modification procedure/method after the next ECM IDLEto ECM CONNECTED transition in response to determining that the wirelessdevice is in the ECM IDLE state and ISR has been activated.

The various embodiments may include or use a dynamic spectrum arbitrageapplication part (DSAAP) protocol and/or component that is configured toallow, facilitate, support, or augment communications between two ormore DSA components (e.g., DPC, DSC, eNodeB, MME, HSS, etc.) so as toimprove the efficiency and speed of the DSA system. A DSA component maybe any component discussed in this application and/or any component thatparticipates in any of the DSA operations, communications, or methodsdiscussed in this application. As such, the DSAAP component(s) may beconfigured to allow, facilitate, support, or augment communicationsbetween any of the components discussed in this application, includingthe communications between a DPC component and a DSC component, betweenthe DSC component and a eNodeB component, between the DSC component andan MME component, between the DSC component and an HSS component,between the MME component and the HSS component, between the eNodeBcomponent and a wireless device, etc.

To facilitate the communications between two or more DSA components, theDSAAP component(s) may publish application programming interfaces (API)and/or include client modules that facilitate communications between theDSA components. In addition, the DSAAP component(s) may be configured toallow the DSA components to communicate specific information, usespecific communication messages, and/or perform specific operations thattogether provide various DSA functions that further improve theefficiency and speed of the DSA system and participating networks.

As an example, the DSAAP component(s) may be configured to allow aneNodeB to communicate with a DSC component (e.g., via the Xe interface),with other eNodeBs (e.g., via an X2 interface), and with various othercomponents (e.g., via the S1 interface). As a further example, the DSAAPcomponent(s) may be configured to allow, facilitate, support, or augmentcommunications between the DSC component and the DPC component so as toallow the DPC and/or DSC components to better pool resources across thedifferent networks, better monitor traffic and resource usage in thevarious networks, to more efficiently communicate bids and biddinginformation, to quickly and efficiently register and deregistercomponents, and better perform backoff operations. The DSAAPcomponent(s) may also improve the DSA resource auctioning operations byimproving the performance and efficiency of the procedures for bidding,generating invoices, advertising resources, requesting resources,purchasing resources, validating bid credentials, etc.

In the various embodiments, all or portions of the DSAAP component maybe included in one or more DSA components, such as a DPC component, aDSC component, an eNodeB component, an MME component, and an HSScomponent. The DSAAP component may be implemented in hardware, software,or a combination of hardware and software. In an embodiment, the DSAAPcomponent may be configured to implement a DSAAP protocol, which may bedefined over the Xe, Xd, and/or X2 reference points. In variousembodiments, the Xe reference point between DSC and eNodeB may use theDSAAP protocol, TR-069 protocol, and/or TR-192 data model extensions tosupport listing available resources at the eNodeB and notifying theeNodeB of bid/buy confirmations. The Xd reference point between DSC andDPC may use the DSAAP protocol for dynamic spectrum and resourcearbitrage operations. The X2 interface/reference point between theeNodeBs may also use the DSAAP protocol to communicate information.

In various embodiments, the DSAAP component(s) may be configured toallow the various DSA components (e.g., DSC, DPC, eNodeB, etc.) tocommunicate using the DSAAP protocol and/or to perform various DSAAPmethods. DSAAP methods may be performed in any of the DSA systemsdiscussed in this application, such as a system that includes a firstDSC server in a first telecommunication network (e.g., a lesseenetwork), a second DSC server in second telecommunication network (e.g.,a lessor network), and a DPC server that is outside of the first andsecond telecommunication networks.

The various embodiments may be implemented on a variety of mobilewireless computing devices, an example of which is illustrated in FIG.21. Specifically, FIG. 21 is a system block diagram of a mobiletransceiver device in the form of a smartphone/cell phone 2100 suitablefor use with any of the embodiments. The cell phone 2100 may include aprocessor 2101 coupled to internal memory 2102, a display 2103, and to aspeaker 2104. Additionally, the cell phone 2100 may include an antenna2105 for sending and receiving electromagnetic radiation that may beconnected to a wireless data link and/or cellular telephone transceiver2106 coupled to the processor 2101. Cell phones 2100 typically alsoinclude menu selection buttons or rocker switches 2107 for receivinguser inputs.

A typical cell phone 2100 also includes a sound encoding/decoding(CODEC) circuit 2108 which digitizes sound received from a microphoneinto data packets suitable for wireless transmission and decodesreceived sound data packets to generate analog signals that are providedto the speaker 2104 to generate sound. Also, one or more of theprocessor 2101, wireless transceiver 2106 and CODEC 2108 may include adigital signal processor (DSP) circuit (not shown separately). The cellphone 2100 may further include a ZigBee transceiver (i.e., an IEEE802.15.4 transceiver) for low-power short-range communications betweenwireless devices, or other similar communication circuitry (e.g.,circuitry implementing the Bluetooth® or WiFi protocols, etc.).

The embodiments described above, including the spectrum arbitragefunctions, may be implemented within a broadcast system on any of avariety of commercially available server devices, such as the server2200 illustrated in FIG. 22. Such a server 2200 typically includes aprocessor 2201 coupled to volatile memory 2202 and a large capacitynonvolatile memory, such as a disk drive 2203. The server 2200 may alsoinclude a floppy disc drive, compact disc (CD) or DVD disc drive 2204coupled to the processor 2201. The server 2200 may also include networkaccess ports 2206 coupled to the processor 2201 for establishing dataconnections with a network 2207, such as a local area network coupled toother communication system computers and servers.

The processors 2101, 2201, may be any programmable microprocessor,microcomputer or multiple processor chip or chips that can be configuredby software instructions (applications) to perform a variety offunctions, including the functions of the various embodiments describedbelow. In some wireless devices, multiple processors 2201 may beprovided, such as one processor dedicated to wireless communicationfunctions and one processor dedicated to running other applications.Typically, software applications may be stored in the internal memory2102, 2202, before they are accessed and loaded into the processor 2101,2201. The processor 2101, 2201 may include internal memory sufficient tostore the application software instructions. In some servers, theprocessor 2201 may include internal memory sufficient to store theapplication software instructions. In some receiver devices, the securememory may be in a separate memory chip coupled to the processor 2101.The internal memory 2102, 2202 may be a volatile or nonvolatile memory,such as flash memory, or a mixture of both. For the purposes of thisdescription, a general reference to memory refers to all memoryaccessible by the processor 2101, 2201, including internal memory 2102,2202, removable memory plugged into the device, and memory within theprocessor 2101, 2201 itself.

The foregoing method descriptions and the process flow diagrams areprovided merely as illustrative examples and are not intended to requireor imply that the steps of the various embodiments must be performed inthe order presented. As will be appreciated by one of skill in the artthe order of steps in the foregoing embodiments may be performed in anyorder. Words such as “thereafter,” “then,” “next,” etc. are not intendedto limit the order of the steps; these words are simply used to guidethe reader through the description of the methods. Further, anyreference to claim elements in the singular, for example, using thearticles “a,” “an” or “the” is not to be construed as limiting theelement to the singular.

The various illustrative logical blocks, modules, circuits, andalgorithm steps described in connection with the embodiments disclosedherein may be implemented as electronic hardware, computer software, orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentinvention.

The hardware used to implement the various illustrative logics, logicalblocks, modules, and circuits described in connection with theembodiments disclosed herein may be implemented or performed with ageneral purpose processor, a digital signal processor (DPC), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but, in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DPC and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DPC core, or any other suchconfiguration. Alternatively, some steps or methods may be performed bycircuitry that is specific to a given function.

In one or more exemplary embodiments, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored as one or moreinstructions or code on a non-transitory computer-readable medium ornon-transitory processor-readable medium. The steps of a method oralgorithm disclosed herein may be embodied in a processor-executablesoftware module which may reside on a non-transitory computer-readableor processor-readable storage medium. Non-transitory computer-readableor processor-readable storage media may be any storage media that may beaccessed by a computer or a processor. By way of example but notlimitation, such non-transitory computer-readable or processor-readablemedia may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that may be used to store desired programcode in the form of instructions or data structures and that may beaccessed by a computer. Disk and disc, as used herein, includes compactdisc (CD), laser disc, optical disc, digital versatile disc (DVD),floppy disk, and blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofnon-transitory computer-readable and processor-readable media.Additionally, the operations of a method or algorithm may reside as oneor any combination or set of codes and/or instructions on anon-transitory processor-readable medium and/or computer-readablemedium, which may be incorporated into a computer program product.

The preceding description of the disclosed embodiments is provided toenable any person skilled in the art to make or use the presentinvention. Various modifications to these embodiments will be readilyapparent to those skilled in the art, and the generic principles definedherein may be applied to other embodiments without departing from thespirit or scope of the invention. Thus, the present invention is notintended to be limited to the embodiments shown herein but is to beaccorded the widest scope consistent with the following claims and theprinciples and novel features disclosed herein.

What is claimed is:
 1. A dynamic spectrum arbitrage (DSA) system,comprising: a home subscriber server (HSS) comprising a HSS processor; amobility management entity (MME) comprising a MME processor coupled tothe HSS via a first communication link; an eNodeB comprising an eNodeBprocessor coupled to the MME via a second communication link; a dynamicspectrum controller (DSC) comprising DSC processor coupled to the eNodeBvia a third communication link; and a dynamic spectrum policy controller(DPC) comprising a DPC processor coupled to the DSC via a fourthcommunication link, wherein the HSS processor is configured withprocessor executable instruction to perform operations comprising:determining whether HSS information stored in a memory of the HSS haschanged for a wireless device; determining whether the changes affectuser profile information stored in a user profile repository of the MMEin response to determining that the HSS information has changed;generating a changed data communication message that includesinformation identifying the changes; and sending the generated changeddata communication message to the MME via the first communication link,and wherein the MME processor is configured with processor executableinstruction to perform operations comprising: receiving the changed datacommunication message via the first communication link; usinginformation included in the received changed data communication messageto determine whether a public data network (PDN) subscription contexthas a related active PDN connection in the MME; determining whether asubscribed quality of service (QoS) profile has been modified; andperforming an subscribed QoS modification.
 2. The DSA system of claim 1,wherein the MME processor is configured with processor executableinstruction to perform operations comprising: adding user profileinformation included in the received changed data communication messageto the user profile repository.
 3. The DSA system of claim 1, whereinthe MME processor is configured with processor executable instruction toperform operations comprising: using information included in thereceived changed data communication message to modify user profileinformation stored in the user profile repository.
 4. The DSA system ofclaim 1, wherein the MME processor is configured with processorexecutable instruction to perform operations comprising: determiningwhether subscription data and a mobile management context of a detachedwireless have been deleted; and sending a purge communication message tothe HSS via the first communication link in response to determining thatthe subscription data and the mobile management context of the detachedwireless have been deleted.
 5. The DSA system of claim 4, wherein theHSS processor is configured with processor executable instruction toperform operations comprising: receiving the purge communication messagevia the first communication link; and setting a purge flag in responseto receiving the purge communication message.
 6. The DSA system of claim1, wherein the DPC processor is configured with processor executableinstruction to perform operations comprising: receiving a resourceswithdrawn communication message from a second DSC indicating that aresource submitted for auction should be withdrawn from the auction; andsending the received resources withdrawn communication message to theDSC via the fourth communication link.
 7. The DSA system of claim 6,wherein the DSC processor is configured with processor executableinstruction to perform operations comprising: receiving the resourceswithdrawn communication message from the DPC via the fourthcommunication link; and sending a request to delete a closed subscribergroup identifier associated with the indicated resource to the eNodeBvia the third communication link.
 8. The DSA system of claim 7, whereinthe eNodeB processor is configured with processor executable instructionto perform operations comprising: receiving the request to delete theclosed subscriber group identifier from the DSC via the thirdcommunication link; updating a list of active resources by removing theclosed subscriber group identifier from the list of active resources;generating a configuration update commutation message that includes theupdated list of active resources; and sending the configuration updatecommutation message to the MME via the second communication link.
 9. TheDSA system of claim 1, wherein: the DSC processor is coupled to the HSSvia a fifth communication link; and the DSC processor is coupled to theMME via a sixth communication link.
 10. The DSA system of claim 9,wherein the HSS processor is configured with processor executableinstruction to perform operations comprising: receiving updated HSSinformation from the DSC via the fifth communication link; anddetermining whether the updated HSS information affects user profileinformation stored in the user profile repository of the MME.
 11. Adynamic spectrum arbitrage (DSA) method of synchronizing information,comprising: determining in a processor of a home subscriber server (HSS)whether HSS information stored in a memory of the HSS has changed for awireless device; determining whether the changes affect user profileinformation stored in a user profile repository of a mobility managemententity (MME) in response to determining that the HSS information haschanged; generating an changed data communication message that includesinformation identifying the changes; sending the generated changed datacommunication message to the MME; receiving the changed datacommunication message in a MME processor of the MME; using informationincluded in the received changed data communication message to determinewhether a public data network (PDN) subscription context has a relatedactive PDN connection in the MME; determining by the MME processorwhether a subscribed quality of service (QoS) profile has been modified;and performing by the MME processor an subscribed QoS modificationoperation in response to determining the subscribed QoS profile has beenmodified.
 12. The DSA method of claim 11, further comprising: addinguser profile information included in the received changed datacommunication message to the user profile repository of the MME.
 13. TheDSA method of claim 11, further comprising: using information includedin the received changed data communication message to modify userprofile information stored in the user profile repository of the MME.14. A home subscriber server (HSS), comprising: a memory; and aprocessor coupled to the memory, wherein the processor configured withprocessor executable instruction to perform operations comprising:establishing a first communication link to a mobility management entity(MME) server; determining whether HSS information stored in the memoryhas changed for a wireless device; determining whether the changesaffect user profile information stored in a user profile repository ofthe MME in response to determining that the HSS information has changed;generating an changed data communication message that includesinformation identifying the changes, including information fordetermining that a subscribed quality of service (QoS) profile has beenmodified for the wireless device; and sending the generated changed datacommunication message to the MME via the first communication link. 15.The HSS of claim 14, wherein the processor is configured with processorexecutable instruction to perform operations further comprising:establishing a second communication link to a dynamic spectrumcontroller (DSC) server; receiving a request for subscriber informationfrom the DSC via the second communication link; and sending the HSSinformation to the DSC in response to receiving the request.
 16. The HSSof claim 14, wherein the processor is configured with processorexecutable instruction to perform operations such that generating thechanged data communication message comprises generating the changed datacommunication message to include information for determining whether apublic data network (PDN) subscription context has a related active PDNconnection in the MME.